Just a note that litestream 0.5 can't handle a 0.3 replica. If you're upgrading from 0.3 to 0.5, you need to restore back to a local sqlite file using 0.3, and then start a new replica on a different path with 0.5.
Also, if you're running litestream in Docker, make sure you're at least locking to an 0.X version, so you don't automatically upgrade to an incompatible version.
Some useful tips for running Django / Wagtail in Cloud Run and Firebase Hosting.
# Cloudrun compatibility https://firebase.google.com/docs/hosting/manage-cache#using_cookies
# "Only the specially-named __session cookie is permitted to pass through to # the execution of your app."
SESSION_COOKIE_NAME = …
This is a helpful bash function to print a command and the time taken.
Note that we need to explicitly use /usr/bin/time to avoid calling the bash built-in time.
time_debug() {
# output the command and real time taken
/usr/bin/time -f "%C # %e seconds" "$@"
}
This site is an experiment in running SQLite in production, with servers that auto-scale to zero.
The key point is to limit the site to a single instance, so any updates are going to one instance of the database.
Litestream is used to replicate the database to/from a storage bucket, providing backup, but also providing a mechanism to scale the app down to zero.