A small homelab that fixes itself (mostly) 0 ▲ TJ Fogarty | Full-Stack AI Engineer 54 minutes ago · 10 min read2095 words · Tech · hide 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 A few constraints shaped everything else: Nothing is public. The box is only reachable over Tailscale. 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… Commenting on Bubbles has been removed. Why? If you want to talk about this post, write to the author, use the comments on their blog if it has them, or reply with a "RE:" post on your own blog. Suggestions? feedback@bubbles.town