Close to ninety containers across four Docker hosts, each with one job. The interesting part is not the list — it is the discipline that keeps a hobby fleet behaving like infrastructure.
Compose definitions live in a version-controlled projects tree and are managed through Arcane; deployments happen from there, nowhere else. Updates are deliberate — watch timers announce new releases, a human decides when to take them — because an unattended update in the wrong place is how a quiet evening becomes a long one. And every service that can fail silently has been taught to fail loudly instead: if a scheduled job degrades, it says so in the first line of the message it sends. Services that live on network storage carry a marker-file gate and cannot start on an empty mount (the mount guard), and every host rotates its own logs on a weekly timer.