https://noraincheck.github.io/tags/sqlite/Recent content in SQLite on NoRaincheckHugoen-USNoRaincheckSun, 01 Mar 2026 00:00:00 +0000https://noraincheck.github.io/posts/a-look-at-campfire-for-self-hosted-slack-alternative/Sun, 01 Mar 2026 00:00:00 +0000https://noraincheck.github.io/posts/a-look-at-campfire-for-self-hosted-slack-alternative/<h2 id="a-look-at-campfire-for-self-hosted-slack-alternative">A look at Campfire for self-hosted Slack alternative</h2> <p><em>March 2026</em></p> <p>Campfire is not really a commonly suggested alternative to Slack/Discord. Afterall its missing various features including voice chat, threads or other features. It makes up for it by being incredibly easy to self-host and easy to write a bot that can interact in such an interface.</p> <p>Campfire can be hosted from a single Dockerfile using sqlite as its database. For majority of low-numbered user-count situations this is more than sufficient.</p>https://noraincheck.github.io/posts/rqlite-a-production-experiment/Wed, 01 Jan 2025 00:00:00 +0000https://noraincheck.github.io/posts/rqlite-a-production-experiment/<h2 id="rqlite---a-production-experiment">rqlite - a Production Experiment</h2> <p><em>January 2025</em></p> <p><code>rqlite</code> is a distributed version of sqlite using the raft consensus algorithm. The great thing about rqlite actually has nothing to do with the underlying tech, but more to do with broad developer experience and that is the defaults with the provided <a href="https://github.com/rqlite/helm-charts/tree/master">helm charts</a>.</p> <p>It just feels like I&rsquo;m the target audience - someone who wants to quickly push <code>rqlite</code> to production with the minimal dependencies and gives me enough to shoot myself in the foot. Compared with <code>postgres</code> helm charts, <code>rqlite</code> presumes that you <em>may</em> want to just use it as-is, without even a values file. That is a welcome change, whereas almost anything from the bitnami one expects you as a developer will make modifications. Something in that model does not <em>feel</em> quite right. This friction (although seemingly trivial) converted me to use <code>rqlite</code> (the other reason is I was using <code>sqlite</code> for my tests which meant I didn&rsquo;t need to worry about changing any code to ensure compatibility between different sql dialects).</p>