<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Server on Tom Meurs</title>
    <link>https://tommeurs.nl/en/tags/server/</link>
    <description>Recent content in Server on Tom Meurs</description>
    <generator>Hugo</generator>
    <language>en</language>
    <copyright>© Tom Meurs</copyright>
    <lastBuildDate>Mon, 18 May 2026 19:30:00 +0100</lastBuildDate>
    <atom:link href="https://tommeurs.nl/en/tags/server/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Backup Strategy for Your Homelab: The 3-2-1 Rule in Practice</title>
      <link>https://tommeurs.nl/en/posts/homelab-backup-strategy/</link>
      <pubDate>Mon, 18 May 2026 19:30:00 +0100</pubDate>
      <guid>https://tommeurs.nl/en/posts/homelab-backup-strategy/</guid>
      <description>&lt;blockquote&gt;&#xA;&lt;p&gt;&lt;strong&gt;TL;DR&lt;/strong&gt; Three copies, two kinds of media, one of them offsite. Restic for files, Velero for the cluster, a Backblaze bucket for the offsite copy, and a restore test on a schedule. Mine costs about €5 a month, and the restore test is the part I still have to make myself do.&lt;/p&gt;&#xA;&lt;/blockquote&gt;&#xA;&lt;p&gt;Picture the disk in your &lt;a href=&#34;https://tommeurs.nl/en/posts/k3s-cluster-setup/&#34;&gt;homelab&lt;/a&gt; dying tonight. Not corrupting, not throwing SMART warnings for a week first, just gone. The git server with every repo you care about, the password vault, fifteen years of family photos, the home automation that runs the house. All of it on a drive that&amp;rsquo;s decided it&amp;rsquo;s done.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Tailscale for Homelab: Secure Remote Access Without Port Forwarding</title>
      <link>https://tommeurs.nl/en/posts/tailscale-homelab/</link>
      <pubDate>Sun, 10 May 2026 18:45:00 +0100</pubDate>
      <guid>https://tommeurs.nl/en/posts/tailscale-homelab/</guid>
      <description>&lt;blockquote&gt;&#xA;&lt;p&gt;&lt;strong&gt;TL;DR&lt;/strong&gt; Tailscale puts every device I own on one WireGuard mesh, so I reach the cluster in the closet from a coffee shop without a single port forwarded on the router. Subnet router, exit node, the Kubernetes operator, ACLs, and Headscale for the part I&amp;rsquo;d rather host myself, in that order.&lt;/p&gt;&#xA;&lt;/blockquote&gt;&#xA;&lt;p&gt;My &lt;a href=&#34;https://tommeurs.nl/en/posts/k3s-cluster-setup/&#34;&gt;homelab cluster&lt;/a&gt; runs in a closet at home. I don&amp;rsquo;t. I work from coffee shops, from a client&amp;rsquo;s office, and now and then from a hotel with WiFi that seems to resent me. I still want my own machines while I&amp;rsquo;m out there.&lt;/p&gt;</description>
    </item>
    <item>
      <title>K3s Cluster Setup on Refurbished Mini-PCs</title>
      <link>https://tommeurs.nl/en/posts/k3s-cluster-setup/</link>
      <pubDate>Fri, 24 Apr 2026 21:12:00 +0100</pubDate>
      <guid>https://tommeurs.nl/en/posts/k3s-cluster-setup/</guid>
      <description>&lt;blockquote&gt;&#xA;&lt;p&gt;&lt;strong&gt;TL;DR&lt;/strong&gt; Three refurbished mini-PCs, K3s with embedded etcd, kube-vip for one API address that survives a dead node, then MetalLB, Traefik and Longhorn on top. About €450 in hardware and an afternoon. Below are the commands, in the order I ran them.&lt;/p&gt;&#xA;&lt;/blockquote&gt;&#xA;&lt;p&gt;Three mini-PCs sit on a shelf in my house. Between them they run my GitLab, my monitoring stack, home automation, file sync, a password manager, and a pile of other things I&amp;rsquo;d rather not hand to someone else&amp;rsquo;s computer. The whole setup cost less than one month of the managed Kubernetes bill for the same thing, and I know what every layer does because I put it there.&lt;/p&gt;</description>
    </item>
    <item>
      <title>NixOS as a Hypervisor: KVM and QEMU Can Do Everything</title>
      <link>https://tommeurs.nl/en/posts/nixos-hypervisor-kvm-qemu/</link>
      <pubDate>Thu, 19 Mar 2026 21:52:00 +0100</pubDate>
      <guid>https://tommeurs.nl/en/posts/nixos-hypervisor-kvm-qemu/</guid>
      <description>&lt;blockquote&gt;&#xA;&lt;p&gt;&lt;strong&gt;TL;DR&lt;/strong&gt; KVM and QEMU are the engine inside Proxmox and most of the cloud you rent. On NixOS, with libvirt on top, that engine is one block of config, and live migration, memory ballooning, GPU passthrough, SR-IOV and CPU pinning are each a command or an XML snippet away. What Proxmox adds is the dashboard and the delegation, and I&amp;rsquo;m honest below about how much that&amp;rsquo;s worth.&lt;/p&gt;&#xA;&lt;/blockquote&gt;&#xA;&lt;p&gt;Ask around how to run a &amp;ldquo;real&amp;rdquo; hypervisor at home and you get the same shortlist. VMware, Hyper-V, or at minimum Proxmox. Something with a web UI, a clustering tab and a marketing page full of enterprise features. The shortlist is so well worn that running VMs without one of those products feels like cutting corners. I don&amp;rsquo;t blame anyone for that. The marketing is good.&lt;/p&gt;</description>
    </item>
    <item>
      <title>CTF and Forensics Skills That Make You a Better DevOps Engineer</title>
      <link>https://tommeurs.nl/en/posts/ctf-skills-for-devops/</link>
      <pubDate>Fri, 27 Feb 2026 19:52:00 +0100</pubDate>
      <guid>https://tommeurs.nl/en/posts/ctf-skills-for-devops/</guid>
      <description>&lt;blockquote&gt;&#xA;&lt;p&gt;&lt;strong&gt;TL;DR&lt;/strong&gt; I spend my evenings on Hack The Box and it&amp;rsquo;s made me better at my day job, which is platform engineering and has nothing to do with pentesting. The first ten minutes on a &lt;span class=&#34;def&#34; tabindex=&#34;0&#34; data-def=&#34;Capture The Flag: a security exercise where you break into a deliberately vulnerable system and prove it by retrieving a planted token, the flag.&#34;&gt;CTF&lt;/span&gt;&#xA; box and the first ten minutes on a broken production server are the same loop, with &amp;ldquo;flag&amp;rdquo; swapped for &amp;ldquo;incident&amp;rdquo;. Below is the toolkit that loop runs on, from one host up to a Kubernetes pod, with the CTF use and the work use side by side for every command.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Simulation, Emulation, Virtualization, and Containers: The Restaurant Metaphor</title>
      <link>https://tommeurs.nl/en/posts/simulation-emulation-virtualization-containers/</link>
      <pubDate>Mon, 23 Feb 2026 20:18:00 +0100</pubDate>
      <guid>https://tommeurs.nl/en/posts/simulation-emulation-virtualization-containers/</guid>
      <description>&lt;blockquote&gt;&#xA;&lt;p&gt;&lt;strong&gt;TL;DR&lt;/strong&gt; Simulation models a thing without running it. Emulation runs it by rebuilding the hardware in software. Virtualization runs several complete operating systems on one machine. Containers run several apps on one kernel. Below, one restaurant per term, a table, and the four mix-ups I hear most.&lt;/p&gt;&#xA;&lt;/blockquote&gt;&#xA;&lt;p&gt;&amp;ldquo;So what&amp;rsquo;s the difference between a container and a virtual machine?&amp;rdquo;&lt;/p&gt;&#xA;&lt;p&gt;I get this question a lot, usually from someone smart who&amp;rsquo;s been nodding along in meetings and doesn&amp;rsquo;t quite want to admit they&amp;rsquo;re fuzzy on it. The honest answer is that most explanations make it worse. They open with &amp;ldquo;hypervisor&amp;rdquo;, &amp;ldquo;kernel sharing&amp;rdquo; and &amp;ldquo;hardware abstraction&amp;rdquo;, and now the person has four new terms to be confused about instead of one.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Zero Trust Explained: The Hotel Key Card Metaphor</title>
      <link>https://tommeurs.nl/en/posts/zero-trust-explained/</link>
      <pubDate>Thu, 19 Feb 2026 21:34:00 +0100</pubDate>
      <guid>https://tommeurs.nl/en/posts/zero-trust-explained/</guid>
      <description>&lt;blockquote&gt;&#xA;&lt;p&gt;&lt;strong&gt;TL;DR&lt;/strong&gt; The old model is a castle. Get past the wall and you&amp;rsquo;re trusted everywhere inside. Zero trust is a hotel. Your key card opens your room, the gym if you booked it, and nothing else, and every door checks the card every time. Below, the three principles, a day in that hotel, and what the key card turns into once the doors are software.&lt;/p&gt;&#xA;&lt;/blockquote&gt;&#xA;&lt;p&gt;&amp;ldquo;So what is this zero trust thing everyone keeps talking about?&amp;rdquo;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Self-Hosting for Everyone: A Vision for Digital Agency</title>
      <link>https://tommeurs.nl/en/posts/self-hosting-for-everyone/</link>
      <pubDate>Tue, 27 Jan 2026 14:00:00 +0100</pubDate>
      <guid>https://tommeurs.nl/en/posts/self-hosting-for-everyone/</guid>
      <description>&lt;p&gt;Most people keep their photos at Google, their mail at Gmail, their documents in whatever cloud came with the phone and their passwords in a browser built by an advertising company. Every byte sits on a server they don&amp;rsquo;t own, under terms they didn&amp;rsquo;t read, in a country they didn&amp;rsquo;t check. Nobody finds that strange anymore, because the alternative looks like a second job.&lt;/p&gt;&#xA;&lt;p&gt;I want to talk about that alternative, and about why it sits behind a wall most people will never climb.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
