infrastructure
Traefik vs nginx: Why I Switched (And Where I Kept Both)
nginx is fine. But when your stack hits 20+ containers, 'fine' stops being enough. Here's how Traefik changed my routing workflow — and where nginx stayed.
homelab
ghost
Setting Up Ghost on a Self-Hosted Server: The Honest Guide
Ghost is good blogging software. It is fast, clean, and does not try to be everything. Setting it up yourself is also one of those tasks that sounds simple, involves several non-obvious decisions, and ends with you having learned something you did not expect to learn. This is how I
homelab
Anatomy of a Homelab: What It Actually Takes to Run 25 Containers at Home
People ask me what a homelab is. I tell them it is the thing you build because you wanted to self-host one small thing, and three years later you are staring at a 20-core server running twenty-five Docker containers while explaining to your family why the internet went down because
homelab
Unraveling the Mystery of the Proxmox OOM Killer: Lessons Learned from the Lab
Earlier this year I wrote about the day Hercules silently died twice before 4pm. The short version: the Linux OOM killer on the Proxmox host decided the 36GB QEMU process for my main VM was the most expendable thing on the machine, and acted accordingly. Twice. That post covered the
homelab
The Tale of the Troublesome Traefik: When Dynamic Configs Go Rogue
Traefik has one feature that makes it genuinely pleasant to work with: hot-reload. Edit a file in the dynamic/ directory, save it, and within seconds the new routes are live. No restart. No downtime. It’s the kind of thing that makes you feel like you have a proper setup.
homelab
Twenty Containers, Twenty Gigabytes: Running Hercules on a Budget
On April 19th, 2026, at 05:13 in the morning, Hercules died. Not dramatically — no error page, no graceful shutdown. The Proxmox host simply ran out of physical RAM, panicked quietly, and had the Linux OOM killer murder the largest QEMU process it could find. That was Hercules. 36GB RSS,
homelab
Running 25 Containers on 20GB: The RAM Budget Reality
In April, Hercules went offline. No warning, no graceful shutdown — just silence. The Proxmox host had run out of physical RAM, the OOM killer had looked around for the fattest process, and found a 36GB QEMU PID with my name on it. The fix was obvious in hindsight: I had
homelab
Running Hercules on a RAM Diet
Hercules runs on a Proxmox host. For a while it had 36GB of RAM allocated. That sounded fine — until the Proxmox host ran out of physical memory, the OOM killer looked around for the fattest process, and selected the QEMU process for Hercules. Gone. No warning, no graceful shutdown. Just
Ghost
Setting up Ghost on a Homelab: The Trust-Proxy Trap and Other Gotchas, Part 1
Setting up Ghost on a Homelab: The Trust-Proxy Trap and Other Gotchas, Part 1 So, you’ve decided to host Ghost in your homelab. Congratulations! You’re about to embark on a journey filled with thrills, chills, and probably some mild exasperation. But fear not. Like a cat prowling its