<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Railway on Wilhelm Maritz</title><link>https://wjmaritz.dev/tags/railway/</link><description>Recent content in Railway on Wilhelm Maritz</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Wed, 22 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://wjmaritz.dev/tags/railway/index.xml" rel="self" type="application/rss+xml"/><item><title>Running SQLite in production (yes, really)</title><link>https://wjmaritz.dev/posts/sqlite-in-production/</link><pubDate>Wed, 22 Jul 2026 00:00:00 +0000</pubDate><guid>https://wjmaritz.dev/posts/sqlite-in-production/</guid><description>&lt;p>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.&lt;/p></description></item></channel></rss>