Attempt to start new version of Ghost during `ghost update` about ghost-cli

[kirrg001]

Some thoughts on this.

First of all, we have to turn the current ghost blog into maintenance mode to avoid any updates to the database. We already have a maintenance flag in Ghost.

One problem with mysql could be that mysqldump is not available, because the executable is not correctly linked, but we could ignore that for the first version and tell the user why auto update wasn't working. Also, there are npm modules out there to dump and insert mysql database via javascript, e.g. https://github.com/webcaetano/mysqldump (deleted the second link)

Furthermore we have to override the database name/filename via env parameter if we start knex-migrator or if we start the new blog.

If a migration happens and it fails, ghost-cli will know, because knex-migrator will fail.
If blog can't start, ghost-cli will know.

[acburdine]

That makes sense. I was thinking "trickier" along the lines of creating a new database might not work if the db user doesn't have the proper permissions. But what we could do in mysql is just dump the db and then try migrating-if that doesn't work then restore the old database from either the dump (if mysql) or the actual db file (if sqlite).

[github-actions]

Our bot has automatically marked this issue as stale because there has not been any activity here in some time. The issue will be closed soon if there are no further updates, however we ask that you do not post comments to keep the issue open if you are not actively working on a PR. We keep the issue list minimal so we can keep focus on the most pressing issues. Closed issues can always be reopened if a new contributor is found. Thank you for understanding 🙂