● Lab · as of 2026-10-30
A home lab that runs itself
The machines, the services and the rules they run by — plus a weekly journal of what changed.
- Containers
- 11
- Health probes
- 13 / 13
- Nightly roll-out
- 04:30
- Backup copies
- 2 ×
- Proxmox VE
- 9.2
- UPS runtime
- ~42 min
01 · How it is run
- 01
Everything is code
If it isn’t in the repo, it isn’t part of the lab. Every change is a reviewed pull request that passes CI.
- 02
Updates take care of themselves
Renovate bumps every pinned version; at 04:30 the node applies main behind a snapshot and rolls back if a health check fails.
- 03
Two copies, two places
Service containers are backed up to the NAS every night, and the NAS’s irreplaceable data is pulled to the node.
- 04
Nothing is exposed
No open ports at home. Private services go over Tailscale; anything public leaves through a single, isolated Cloudflare Tunnel — never a port forward.
- 05
Alerts, not dashboards
Every service is probed; failures, failing disks and UPS events reach the phone within minutes.
02 · What runs here
- Proxmox VE + LXC
- one container per service, a snapshot before every update
- Harbor
- private registry, signed images (cosign), vulnerability scans
- Prometheus · Grafana · ntfy
- metrics, dashboards, alerts on the phone
- AdGuard Home ×2
- DNS plus ad and malware blocking for every device
- Caddy + Tailscale
- real certificates and the same names at home and away
- Vaultwarden
- passwords, reachable only over the tailnet
- Renovate + GitHub Actions
- every version pinned, then bumped and merged automatically
- n8n + GLM
- the automation that writes this site’s news
03 · Lab Journal
What changed in the lab, week by week — written from the real changes, with private details removed.