In order to more properly deal with server migrations, the blog needs to have a read-only mode where data writes are rejected (or better still, never issued) and access to the site remains limited to browsing data (and possibly sending email).
Implications:
READ_ONLY setting in local_settings.py
context processor that exposes the value to the template engine
decorator for views that write data which returns an error page when READ_ONLY is set to True
A significant portion of the blog can remain operable with read-only access to the database:
home page, article lists, article pages, profiles, about, links, etc.
feedback form (doesn't touch the DB)
RSS feeds
API
Other areas will be disabled and return an error page:
any form other than the feedback form
login, registration, and sessions
If anyone thinks of another consideration, feel free to leave a comment.
In order to more properly deal with server migrations, the blog needs to have a read-only mode where data writes are rejected (or better still, never issued) and access to the site remains limited to browsing data (and possibly sending email).
Implications:
READ_ONLYsetting inlocal_settings.pyREAD_ONLYis set toTrueA significant portion of the blog can remain operable with read-only access to the database:
Other areas will be disabled and return an error page:
If anyone thinks of another consideration, feel free to leave a comment.