Ideas around this

• I think integrating a particular web app server that can be controlled by the web app itself would work.
  • Essentially a boomerang effect. The web app tells the web app server to restart the web app.
  • I have just run some experiments on this, and uwsgi can do exactly what we want.
  • Within the web app, just import uwsgi and then call uwsgi.reload()
  • The best way of doing this would probably be to fire off some sort of task that runs after the request has been finished. Reason is that we can then return a webpage that says the website is being reloaded, and then redirect the user to the homepage. As soon as the website has reloaded, the request for the homepage will be fulfilled (uwsgi has graceful reloading, so it will just queue up requests whilst reloading the web app).
  • Note reloading would work fine for updates that don't involve the db. However, for updates involving the db, we would need to:
  • Stop the web app
  • Make a backup (if possible) of the db, or at least work on it in a transaction
  • Migrate the db
  • Handle failures by restoring db to original state
  • If successful, start the web app again
  • Alternatively, we could only run restarts like this when it is a simple non-db-migration update
  • Considering that atm only I use this blog, It would work fine for me to just have a page that lets me reload the website.
  • Note that the other use of reloading/restarting is that settings like persona.siteName will get applied.
  • See http://uwsgi-docs.readthedocs.org/en/latest/Spooler.html and http://uwsgi-docs.readthedocs.org/en/latest/PythonDecorators.html

from fireblog.

I have created a reload view, but now just need to link to it in the navbar

from fireblog.