Laptop-to-Desktop Failover Needs Agent State, Not Hope
A second worker is useful only if it knows what the first worker already changed.
homelab
One Ingress Is Easier to Reason About Than Three
Every extra reverse proxy adds another place for routing, TLS and headers to disagree.
Three Caddy Instances Can All Be Healthy While Nobody Knows Which One Owns the Request
Multiple proxies are fine when each boundary has one explicit owner.
Why Tailscale Became the Control Plane for My Home Infrastructure
I do not use Tailscale as a generic VPN. I use it as the stable identity and reachability layer between my laptop, desktop and home server.
A Home Server Became Production the Day I Needed a Recovery Time
The difference between a lab box and production infrastructure is not the hardware; it is whether failure has a documented recovery path.
A Year of Small Network Labs: What Broke Most Often
Most beginner lab failures were not exotic protocol bugs. They were wrong masks, wrong VLANs, missing routes, stale assumptions and tests that did not isolate the failing layer.
Linux Routing Tables: The Moment `ip route` Replaced Guessing
Once I started reading Linux routes as prefix decisions instead of interface settings, multi-interface hosts and lab gateways became much easier to debug.
Building a Small Home Lab from an Old PC and a Cheap Switch
A useful home lab does not need enterprise hardware. A spare PC, a small switch and a few isolated network experiments are enough to learn a lot about real interfaces, routes and services.
SSH Keys Made My Home Lab Feel Like a Real Network
Moving from local console access to SSH keys changed the lab from a collection of machines into something I could actually operate and troubleshoot remotely.