Posts

Your homelab runs your GitLab, your passwords, your photos, your home automation. What happens when the disk fails? If you can’t answer that question confidently, you don’t have backups. You have hope. The 3-2-1 rule has been around for decades because it works. Three copies, two different media, one offsite. Here’s how to actually implement it. The 3-2-1 Rule Explained flowchart TD subgraph rule["3-2-1 Backup Rule"] Data["Original Data"] subgraph three["3 Copies"] C1["Copy 1<br/>(Original)"] C2["Copy 2<br/>(Local Backup)"] C3["Copy 3<br/>(Offsite)"] end subgraph two["2 Media Types"] M1["NVMe/SSD"] M2["HDD/NAS"] end subgraph one["1 Offsite"] Off["Cloud/Remote"] end end Data --> C1 Data --> C2 Data --> C3 C1 --> M1 C2 --> M2 C3 --> Off Why Three Copies? Copy 1: Your live data (original) Copy 2: Local backup (fast restore) Copy 3: Offsite backup (disaster recovery) One copy is not a backup. Two copies can both fail in the same disaster (fire, flood, ransomware). Three copies with separation gives you real resilience. ...

You SSH into a server. You start a long-running process. Your connection drops. Process dies. Terminal multiplexers solve this. They keep sessions alive, split your screen into panes, and let you work on multiple things without opening twelve terminal windows. I’ve used all three major options. Here’s what I learned. What Is a Terminal Multiplexer? A terminal multiplexer runs between your shell and terminal emulator. It: Persists sessions: Detach, reconnect later, everything still running Splits screens: Multiple panes in one window Manages windows: Switch between workspaces Works remotely: Same interface whether local or SSH’d flowchart LR Term["Terminal Emulator"] --> Mux["Multiplexer"] Mux --> Shell1["Shell 1"] Mux --> Shell2["Shell 2"] Mux --> Shell3["Shell 3"] GNU Screen: The Original Screen has been around since 1987. It’s installed everywhere, it works, it’s ugly. ...

Your homelab cluster runs at home. You’re not always at home. You need access. The traditional approach: forward ports, set up dynamic DNS, configure firewall rules, pray nobody finds your exposed services. The better approach: Tailscale. Zero exposed ports. Secure WireGuard encryption. Your devices find each other, wherever they are. What Is Tailscale? Tailscale is a mesh VPN built on WireGuard. Every device gets a stable IP. Every device can reach every other device. No central server routing your traffic. ...

Every platform team eventually asks: should we build an Internal Developer Platform? The answer is probably yes. The question is how. I’ve seen platforms that cost millions and never got adopted. I’ve also seen scrappy internal tools that transformed developer productivity overnight. The difference isn’t budget or technology — it’s approach. What Is an Internal Developer Platform? An Internal Developer Platform (IDP) is a self-service layer that abstracts infrastructure complexity from developers. Instead of writing Kubernetes YAML, developers describe what they need. The platform handles how. ...

You have Grafana. You have Prometheus metrics. You have logs in Loki and traces in Tempo. You also have 47 dashboards that nobody looks at. Dashboard rot is real. Teams create dashboards for every possible metric, every service, every potential issue. Six months later, nobody remembers what half of them show or why they exist. Good dashboards are different. They get opened daily. They answer questions before you ask. They help you understand your system, not just display numbers. ...