A small homelab that fixes itself (mostly) A homelab operator running Ubuntu Server on an Intel N100 mini PC with 16 GB of RAM has wired Claude Code into the alerting path so the AI coding agent can act on container failures before the owner checks his phone. The setup keeps every app in its own folder under /srv/stacks// with a single compose file, binds ports only to the Tailscale IP or 127.0.0.1, sets a memory limit on every service, and runs scheduled jobs from the user crontab rather than systemd units because passwordless sudo is disabled — a constraint the author notes limits what an automated process can do. Caddy fronts the apps with a wildcard Let's Encrypt certificate obtained via the Cloudflare DNS-01 challenge, while AdGuard Home rewrites *.home. to the box's Tailscale IP so names resolve only inside the network. A small homelab that fixes itself mostly How I deploy apps, keep an eye on containers, and hand alerts to Claude Code so it can fix things while I'm away from the keyboard. I have a little mini PC living in my office. It’s a humble box with an Intel N100 and 16 GB of RAM, running Ubuntu Server. I bought it years ago, so I don’t want to know how much it sells for today. It runs a handful of apps for the house: some media tooling, Home Assistant, a document archive, network-wide ad blocking, and a few things I’ve built myself. I’m not going to go through the apps. They come and go. What I wanted to write down is the boring part underneath: how an app gets deployed, how I find out when something breaks, and how I’ve started letting Claude Code deal with problems before I even look at my phone. the-rules The rules A few constraints shaped everything else: - Nothing is public. The box is only reachable over Tailscale https://tailscale.com . There’s no port forwarding and no tunnels. If I’m not on the tailnet, it doesn’t exist. - It’s a small machine. An N100 is great for the power draw but slow at building images. Containers need to be lean, and I’d rather pull an image than build one. - Every app gets the same shape. One folder, one compose file. - No passwordless sudo. Scheduled jobs live in my user crontab, not in systemd units. That matters later, because it limits what an automated process can actually do. deploying-an-app Deploying an app Every app lives in its own directory under /srv/stacks/