Skip to content
Radoslav Gatev edited this page Jan 21, 2018 · 5 revisions

Will pushing/merging to my repo cause an immediate deployment?

It depends on the isManualIntegration property of your Web App resouce. If you deployed using the azuredeploy.json template in this repo this property will be set to true. True means that it won't be automatically deployed. Otherwise it will set up a webhook to do automatic deployments.

You can check this in your Web App resource using Azure Resource Explorer. It is located under subscriptions/{YOUR_SUBSCRIPTION}/resourceGroups/{YOUR_RESOURCE_GROUP/providers/Microsoft.Web/sites/{YOUR_WEB_APP_NAME}/sourcecontrols/web

How to upgrade your blog?

Recommended prerequisite: Although the default behavior of Deployment options is to persist the files not included in the repository, I tend to back up my database by downloading it. You can use your preferred method for doing backups.

  1. Merge solvsoftware/Ghost-Azure with your fork.
  2. Make sure WEBSITE_NODE_DEFAULT_VERSION app setting is set to whatever the value is in Resource template. By the time of writing it is 8.9.3.
  3. Execute npm rebuild to rebuild the packages in order to be used with the current version of Node.js.(Not needed if you didn't change the version in Step 2.)
  4. Execute the following version of db.js in order to update the database. This will make a copy of your database before starting the process.
var KnexMigrator = require('knex-migrator');
var knexMigrator = new KnexMigrator({
    knexMigratorFilePath: __dirname
});

//knexMigrator.init();
knexMigrator.migrate();
Clone this wiki locally