Operations for the machine underneath — a Matrix homeserver, Element Call and the family's websites, run on a 2012 Mac mini, with the runbook and the live status dashboard treated as part of the system.
iantalabs/family-server-ops · private, in active useMatrix/Synapse · Docker · nginx · Cloudflare Tunnel
A real homeserver, not a toy. Matrix, video calling and public sites run behind a tunnel, with the media store and the database deliberately on different disks.
A live operations dashboard, admin-gated: current status of the server and the sites it serves, denied on the public listener and reachable only over the private network.
Decisions are written down. A standing rule to read the decision log before changing anything non-trivial — several choices look wrong until you know what was ruled out.
Nine corruption incidents traced to one root cause — a database living on the wrong filesystem — and migrated off it. The incident record is part of the repo, not separate from it.
This site deploys through it. One script builds and ships each site, then verifies the result at every URL it is meant to answer on.
The runbook front-end. Every card is rendered from the ops repo's own checkout, never copied.
Unglamorous and load-bearing. An AI Nation that cannot keep its own comms up is a slide
deck, so the substrate is in the portfolio on purpose.
The site you are reading is deployed by this repo's tooling, onto that machine.
Interested in any of this?
The tools are in private use while they are built. If something here is worth
a conversation — the Desk, the shared surface, or how the pieces fit into an
AI Nation — the way in is a message on LinkedIn.