Diary of a Weekend Linux Warrior

About

Who writes this and what runs it.

I’m Diego. During the week I work on developer platforms, meaning the tooling and infrastructure other engineers build on top of, with a lot of it lately pointed at security and AI. On weekends I run one server in a closet and write down what happens to it.

The subject matter is Linux, home lab hardware, and running AI on machines I own rather than rent. All three reward patience and punish assumptions, and the interesting part is usually the failure rather than the finished setup. That is what most of these entries are about.

The lab, currently

One Proxmox node. That is the entire cluster, which means I have spent more time than I expected thinking about what happens while it reboots.

Nothing on it is clicked into being. Terraform builds the infrastructure, Ansible configures it, and Semaphore watches the repository and applies whatever landed on main within fifteen minutes. If it is not in the repo, it does not survive a rebuild. That rule has cost me a few evenings and saved me a lot more.

What runs there: DNS and ad blocking, Home Assistant, a metrics stack, log aggregation, a reverse proxy terminating TLS for everything internal, a media server, a file share, and a VM I keep for AI agent experiments. Backups land on a NAS overnight. The current list is on what I’m running.

What is not here, on purpose: addresses, internal hostnames, and the shape of the network. This page is public. The map is not.

Elsewhere

Corrections and arguments are welcome. The fastest way to reach me is GitHub.