Running a homelab like production
My homelab started as a pile of containers I poked at until they worked. This series follows what changed once I treated it like production: every change goes through code, alerts tell me when something breaks, backups get restored on purpose, and tuning starts from a measurement.
- Running a one-server homelab like production
Why run a one-server homelab like production infrastructure?
- Structuring an Ansible repo for a one-server homelab
How do I structure an Ansible repo for a single-server homelab?
- Homelab deploys with Forgejo Actions and Semaphore
How do I deploy a homelab from git with Forgejo Actions and Semaphore?
- Time Machine backups on a Samba share in Docker
How do I back up a Mac to a Samba share with Time Machine, and know when it silently stops?
- What the ZFS ARC does with your RAM, and what a cap costs
How much RAM does the ZFS ARC take on a homelab server, and what changes when you cap it?