skip to content a landlocked captain’s log
- A lifeboat for every hull Every project I run has a git remote, so the code survives a dead machine. The databases, uploaded files and secrets do not. This is the backup system I built into Control Room in a day. Control Room owns the config; a separate agent holds the credentials and does the dumps; the sensitive one is encrypted; and one screen shows whether every project has a current copy off the box. infrastructure · control · postgres · ssh · age · zstd
- What changed since you last played Steam already shows a combined news feed for the games you own, but you cannot search or filter it and the ordering barely makes sense. Here is the feed I built for Playtopia.com.au instead, with the same official posts sorted properly, made searchable and filterable, and everything published since you last played each game marked. infrastructure · nextjs · react · steam-api
- The chart room How I keep twenty-odd projects, five machines, and two AI agents in sync from a single dashboard built entirely out of plain Markdown and YAML files. The folder layout, why every status check is recomputed live instead of stored, and the plain-text handoff format that lets two agents continue each other's work. control · standards · docker · git · yaml · nextjs
- A key with one job A container needed to read three remote machines over SSH without holding a key that could also root them. The exact authorized_keys options that pin a key to one read-only command and a single permitted tunnel, what each one does, and the break-in tests that prove it holds. Copy it for anything that has to phone home from inside a container. infrastructure · openssh · docker
