Hero Image
The SQLite trap caught me the same day I wrote about it

I recently published a post about running SQLite in production, and the heart of it was a warning: on a platform with an ephemeral filesystem, a mis-pointed SQLite file means your database quietly ceases to exist on every redeploy. I even described my defence with some pride. The app refuses to accept a raw connection string and builds its own from a SQLITE_DIR environment variable, so nobody can get the path wrong.

Thursday, July 23, 2026 | 4 minutes Read
Hero Image
Running SQLite in production (yes, really)

I recently shipped a small Flask app, a scoring platform for a fitness competition, with SQLite as its only database. Not as a stopgap until the real database arrives: the app refuses to start with anything else, because a half-supported second database is worse than none. The conventional advice says this is a mistake. For this class of app, the conventional advice is wrong, but the deployment details will bite you if nobody warns you about them.

Wednesday, July 22, 2026 | 5 minutes Read