<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Self-Hosting - Tag - Botmonster Tech</title><link>https://botmonster.com/tags/self-hosting/</link><description>Self-Hosting - Tag - Botmonster Tech</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Sun, 14 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://botmonster.com/tags/self-hosting/" rel="self" type="application/rss+xml"/><item><title>Node vs Bun vs Deno in 2026: The Self-Hosting Verdict</title><link>https://botmonster.com/web-dev/best-javascript-runtimes-2026/</link><pubDate>Sun, 14 Jun 2026 00:00:00 +0000</pubDate><author>Botmonster</author><guid>https://botmonster.com/web-dev/best-javascript-runtimes-2026/</guid><description><![CDATA[<div class="featured-image">
                <img src="/best-javascript-runtimes-2026.png" referrerpolicy="no-referrer">
            </div><p>For self-hosting real apps in 2026, pick Node.js 24 LTS for stable long-running processes, Bun 1.3 for install speed, and Deno 2.8 for single-binary deploys. On my own box, Bun installs an 847-package monorepo in 1.2 seconds versus npm&rsquo;s 32, but Node still wins the 3am stability test.</p>
<section class="key-takeaways">
  <h2 id="key-takeaways" class="key-takeaways-title">
    <svg class="key-takeaways-icon" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true">
      <rect x="4" y="3" width="16" height="18" rx="2" ry="2"></rect>
      <path d="M8 8h5"></path>
      <path d="M8 13h8"></path>
      <path d="M8 17h8"></path>
      <path d="M15.5 7l1.2 1.2L19 6"></path>
    </svg>
    <span>Key Takeaways</span>
  </h2>
  <div class="key-takeaways-body">
<ul>
<li>Node.js 24 LTS stays the safest default for long-running production processes.</li>
<li>Bun installs dependencies 20 to 40 times faster than npm in real projects.</li>
<li>Deno compiles to a single 28MB binary, the simplest self-host deploy there is.</li>
<li>Node now ships a test runner, watch mode, and TypeScript, closing the gap.</li>
<li>Native C/C++ addons work in Node and Bun but not in Deno.</li>
</ul>

  </div>
</section>

<p>Three runtimes now fight for the same job: running your server-side JavaScript. <a href="https://nodejs.org/" target="_blank" rel="noopener noreferrer ">Node.js</a>
 is the 16-year incumbent. <a href="https://bun.com/" target="_blank" rel="noopener noreferrer ">Bun</a>
 bets on raw speed. <a href="https://deno.com/" target="_blank" rel="noopener noreferrer ">Deno</a>
 bets on security and a single binary. This post compares them for one specific use: self-hosting a real app on hardware you own, not a synthetic hello-world race.</p>]]></description></item><item><title>Self-Hosted Databases in 2026: Postgres vs SQLite vs MariaDB</title><link>https://botmonster.com/self-hosting/self-hosted-databases-postgres-sqlite-mariadb/</link><pubDate>Sat, 13 Jun 2026 00:00:00 +0000</pubDate><author>Botmonster</author><guid>https://botmonster.com/self-hosting/self-hosted-databases-postgres-sqlite-mariadb/</guid><description><![CDATA[<div class="featured-image">
                <img src="/self-hosted-databases-postgres-sqlite-mariadb.png" referrerpolicy="no-referrer">
            </div><p>Picking a self-hosted database in 2026 comes down to one question: when does it force you to migrate? SQLite holds until about one write-heavy app server (~10 GB, single writer). PostgreSQL 18 is the default that almost never makes you move. MariaDB 12.3 LTS earns its spot mainly when you already live in the MySQL world.</p>
<section class="key-takeaways">
  <h2 id="key-takeaways" class="key-takeaways-title">
    <svg class="key-takeaways-icon" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true">
      <rect x="4" y="3" width="16" height="18" rx="2" ry="2"></rect>
      <path d="M8 8h5"></path>
      <path d="M8 13h8"></path>
      <path d="M8 17h8"></path>
      <path d="M15.5 7l1.2 1.2L19 6"></path>
    </svg>
    <span>Key Takeaways</span>
  </h2>
  <div class="key-takeaways-body">
<ul>
<li>SQLite serializes writes, so one busy app server is its real ceiling.</li>
<li>Postgres 18 is the default that almost never makes you migrate later.</li>
<li>MariaDB fits best when you already run MySQL tooling.</li>
<li>SQLite runs with no daemon and almost no RAM, while Postgres needs tuning.</li>
<li>The SQLite to Postgres jump is a planned move, not an emergency.</li>
</ul>

  </div>
</section>

<h2 id="what-are-the-best-self-hosted-databases-for-web-apps-in-2026">What are the best self-hosted databases for web apps in 2026?</h2>
<p>For a self-hosted web app, three engines cover almost every case: <a href="https://www.postgresql.org/" target="_blank" rel="noopener noreferrer ">PostgreSQL</a>
 is the do-everything default, <a href="https://sqlite.org/" target="_blank" rel="noopener noreferrer ">SQLite</a>
 is the embedded single-file engine, and <a href="https://mariadb.org/" target="_blank" rel="noopener noreferrer ">MariaDB</a>
 is the MySQL-compatible community fork. All three are open source and free to run on your own box.</p>]]></description></item><item><title>Podman vs Docker for Self-Hosting: I Measured the Difference</title><link>https://botmonster.com/self-hosting/podman-vs-docker-linux-container-runtime/</link><pubDate>Sat, 11 Apr 2026 00:00:00 +0000</pubDate><author>Botmonster</author><guid>https://botmonster.com/self-hosting/podman-vs-docker-linux-container-runtime/</guid><description><![CDATA[<div class="featured-image">
                <img src="/decentralized-village-vs-centralized-city.png" referrerpolicy="no-referrer">
            </div><p>For self-hosting on Linux in 2026, <a href="https://podman.io/" target="_blank" rel="noopener noreferrer ">Podman</a>
 is <strong>the better default</strong>. It has no daemon, runs rootless out of the box, and its Quadlet unit files make containers behave like any other systemd service on your box. I say that as someone whose own stack still runs on <a href="https://www.docker.com/" target="_blank" rel="noopener noreferrer ">Docker</a>
. After years of reading that Podman is lighter, faster, and safer, I installed it next to Docker and measured the difference on my own hardware. Some claims held up: rootless Podman with pasta networking (Podman&rsquo;s user-mode network layer) beat rootful Docker&rsquo;s bridge on download throughput in every run. There is also no daemon holding memory between deployments. One claim did not survive: the often-repeated &ldquo;Podman starts containers about 50 ms faster&rdquo; was <strong>a statistical tie</strong> on my machine.</p>]]></description></item></channel></rss>