DARNI.ORG — Recent posts

4 min readhomelabdnspiholetroubleshootingdockersqlite

How Pi-hole Protected Itself and Killed the Network

I have grown used to dirty power at this point. The grid fails, you wait fifteen minutes for it to stabilize, and then you power the server back on just for the power to go off again.

8 min readhomelablxcproxmoxansibleopentofulinuxtroubleshooting

Teaching an LXC to Drive a Monitor And Why I Killed It

After dealing with a 15GB Traefik log file that quietly filled my server to 95% capacity last week, I had a thought: if I had a dashboard I could just glance at, I would have caught the storage spike days before it became an emergency.

5 min readhomelabtroubleshootingtraefiktailscaleproxmox

A Week of Incidents: Logs, Keys, and Dirty Power

There is a specific kind of hubris that builds up when your homelab runs smoothly for almost a year. You start trusting your own setup. You start thinking your architecture is actually solid.

7 min readhomelabobservabilitymonitoringprometheusgrafanalokiproxmoxspring-boot

Instrument What You Can't See

At the end of my DeepDame writeup I mentioned something almost in passing: the backend was designed for an LGTM observability stack, and in production it ran on a single VM on a desktop in my room. Both halves of that are still true.

24 min readdeepdameflutterspring bootreal-timewebsocketsleadershipretrospectivehome lab

DeepDame: Two Semesters, Two Halves of a System

DeepDame is a real-time multiplayer checkers game. We built it across two semesters, five of us, at FST Settat. The repo is public. The APK works.

15 min readhome labproxmoxdockersystems engineeringnetworkingarch linuxself-hosted

Architecting a Modular Home Lab: A Systems Engineering Playground

Every computer science student knows the lingering anxiety of executing a complex command on their primary workstation.

7 min readhome labproxmoxdockerlxcnfsself-hostedmedia server

My Arr Stack Setup: Proxmox, LXCs, and NFS Workarounds

This blog exists for one primary reason: to serve as documentation for future-me. Debugging a broken server configuration months down the line when you have zero memory of what you originally did is an absolute nightmare.