<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Selfhosting on Linux Café</title>
    <link>https://mrtomlinux.org/tags/selfhosting/</link>
    <description>Recent content in Selfhosting on Linux Café</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Wed, 04 Nov 2026 08:25:42 +0200</lastBuildDate>
    <atom:link href="https://mrtomlinux.org/tags/selfhosting/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Automating Let&#39;s‑Encrypt renewal on a single‑node web server without downtime</title>
      <link>https://mrtomlinux.org/post/2026-11-04-automating-letsencrypt-renewal-on-a-singlenod/</link>
      <pubDate>Wed, 04 Nov 2026 08:25:42 +0200</pubDate>
      <guid>https://mrtomlinux.org/post/2026-11-04-automating-letsencrypt-renewal-on-a-singlenod/</guid>
      <description>&lt;h2 id=&#34;automating-lets-encrypt-renewal-on-a-singlenode-web-server-without-downtime&#34;&gt;Automating Let’s Encrypt renewal on a single‑node web server without downtime&lt;/h2&gt;&#xA;&lt;p&gt;Let’s Encrypt certificates expire every 90 days. On a single‑node web server the usual approach is to run &lt;code&gt;certbot renew&lt;/code&gt; from cron and reload the web service. The trick is to avoid any traffic loss while the new cert is in place. Below is a minimal, production‑ready recipe that works with Apache, Nginx, or any systemd‑managed web server.&lt;/p&gt;&#xA;&lt;h3 id=&#34;1-install-certbot-and-the-webroot-plugin&#34;&gt;1. Install Certbot and the web‑root plugin&lt;/h3&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; class=&#34;chroma&#34;&gt;&lt;code class=&#34;language-bash&#34; data-lang=&#34;bash&#34;&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;&lt;span class=&#34;c1&#34;&gt;# Debian/Ubuntu&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;sudo apt-get install certbot python3-certbot-nginx   &lt;span class=&#34;c1&#34;&gt;# or python3-certbot-apache&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;&lt;span class=&#34;c1&#34;&gt;# RHEL/CentOS&lt;/span&gt;&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;sudo dnf install certbot python3-certbot-nginx&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;The &lt;code&gt;nginx&lt;/code&gt; or &lt;code&gt;apache&lt;/code&gt; plugin automatically configures the web‑root challenge and reloads the server after a successful renewal.&lt;/p&gt;</description>
    </item>
    <item>
      <title>When a VPS Disk Fills Mid‑Night: Quick Recovery with LVM Snapshots and Automated Alerts</title>
      <link>https://mrtomlinux.org/post/2026-11-02-when-a-vps-disk-fills-midnight-quick-recovery/</link>
      <pubDate>Mon, 02 Nov 2026 10:41:28 +0200</pubDate>
      <guid>https://mrtomlinux.org/post/2026-11-02-when-a-vps-disk-fills-midnight-quick-recovery/</guid>
      <description>&lt;p&gt;Disk‑full crashes are the most common reason a VPS goes from “alive” to “dead” overnight.&lt;br&gt;&#xA;A log file or a database that blows past the allotted space will make the kernel refuse&#xA;any further writes, and every process that needs to touch the disk will start failing.&#xA;If you’re running a website, mail server, or database, that’s a service outage you can’t afford.&lt;/p&gt;&#xA;&lt;p&gt;The silver lining? A handful of LVM tricks and a tiny monitoring script can get you back up in minutes and keep future incidents at bay.&lt;br&gt;&#xA;Below I walk through a real‑world scenario on a Debian‑based VPS, but the ideas carry over to any distro that uses LVM and systemd.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Rootless Podman volumes: how to keep data safe across upgrades without root</title>
      <link>https://mrtomlinux.org/post/2026-11-01-rootless-podman-volumes-how-to-keep-data-safe/</link>
      <pubDate>Sun, 01 Nov 2026 10:54:24 +0200</pubDate>
      <guid>https://mrtomlinux.org/post/2026-11-01-rootless-podman-volumes-how-to-keep-data-safe/</guid>
      <description>&lt;h2 id=&#34;rootless-podman-volumes-keeping-your-data-safe-across-upgrades&#34;&gt;Rootless Podman Volumes: Keeping Your Data Safe Across Upgrades&lt;/h2&gt;&#xA;&lt;p&gt;Rootless Podman lets you run containers without ever touching &lt;code&gt;sudo&lt;/code&gt;.&lt;br&gt;&#xA;That’s great, but it also means every volume lives in your home directory.&lt;br&gt;&#xA;When you bump Podman or your distro, the storage layout can change and &lt;em&gt;all&lt;/em&gt; your data can get wiped.&lt;br&gt;&#xA;Below is a practical, coffee‑talk style walk‑through that shows how to sidestep this trap.&lt;/p&gt;&#xA;&lt;hr&gt;&#xA;&lt;h3 id=&#34;why-rootless-volumes-are-different&#34;&gt;Why Rootless Volumes Are Different&lt;/h3&gt;&#xA;&lt;p&gt;When you run&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
