Look into some sort of auto update mechanism about fireblog HOT 3 CLOSED

Alternatively, we could focus around git and github being the update mechanisms:

The blog could check github to see either if there has been a new release or if the develop branch is ahead. If so, then we pull in the new commits, then reload.

But we need to know if there are any db changes required. This could be done by running alembic in a new python process to check if the db is up-to-date or not. If not, then we need to shut down, back up db, migrate db, start uwsgi. If migration fails, then fallback to last working commit, use the backed up db as the actual db.

Alternatively, we could just dump the responsibility of doing db migrations onto the user and only handle updates that are straightforward.

It would also be nice to have info on what has changed, although this could simply be done by showing the last commit message and having a master branch only for deployments.

from fireblog.

I plan on closing this issue once I've gotten round to testing this for real.

from fireblog.

I have tested this by cloning the repo, cloning the clone, and usinng the first clone as a master, making sure the 2nd clone picked up on the changes, and was able to update.

from fireblog.