<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Incidents on Wilhelm Maritz</title><link>https://wjmaritz.dev/tags/incidents/</link><description>Recent content in Incidents on Wilhelm Maritz</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Thu, 23 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://wjmaritz.dev/tags/incidents/index.xml" rel="self" type="application/rss+xml"/><item><title>The SQLite trap caught me the same day I wrote about it</title><link>https://wjmaritz.dev/posts/sqlite-trap-epilogue/</link><pubDate>Thu, 23 Jul 2026 00:00:00 +0000</pubDate><guid>https://wjmaritz.dev/posts/sqlite-trap-epilogue/</guid><description>&lt;p>I recently published &lt;a href="https://wjmaritz.dev/posts/sqlite-in-production/">a post about running SQLite in production&lt;/a>, 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 &lt;code>SQLITE_DIR&lt;/code> environment variable, so nobody can get the path wrong.&lt;/p></description></item></channel></rss>