📘 Volume 4 — Home Lab
Make it programmable. Docker, VMs, networking, monitoring. The volume that turns the NAS into a development platform.
Volumes 1-3 built a NAS for family + creator use. This volume takes the next step: what if the NAS also runs a home lab? Docker containers for self-hosted services, VMs for development and testing, networking for the technically curious, monitoring for the operations-minded. The principles from Volume 1 still apply (snapshots, scrubs, the data hierarchy) — this volume adds the compute and orchestration layers.
What this volume covers
The home lab is a different mindset from the family NAS. The family NAS is about safety and stability. The home lab is about exploration and learning. The two coexist on the same hardware; the discipline is keeping them separate.
- The lab as a system — separating the family data from the lab experiments
- Networking fundamentals — VLANs, subnets, the model of a home network
- Virtualization — VMs vs containers, when to use which
- Docker and containers — running self-hosted services the right way
- VMs with KVM — for development, testing, and full operating systems
- Reverse proxies and TLS — exposing services securely
- Monitoring — knowing when things are broken
- Home automation — Home Assistant, MQTT, the smart home layer
- When to expand — second NAS, Proxmox cluster, the right time to grow
Chapters
📖 Ch 01 · The Lab as a System
Separating the family data from the lab experiments. The "blast radius" of a mistake. The dataset boundaries.
10 min read📖 Ch 02 · Networking Fundamentals
IPs, subnets, VLANs, DHCP, DNS, the model of a home network. Why the lab needs its own subnet.
15 min read📖 Ch 03 · Virtualization
VMs vs containers. When to use each. The mental model that makes the choice obvious.
12 min read📖 Ch 04 · Docker and Containers
Docker, Docker Compose, container orchestration for the home. The "docker-compose.yml" pattern.
15 min read📖 Ch 05 · VMs with KVM
When a container isn't enough. KVM, virt-manager, the right tool for full operating systems.
12 min read📖 Ch 06 · Reverse Proxies and TLS
Traefik, Caddy, Nginx. Exposing services to the internet with HTTPS, the right way.
12 min read📖 Ch 07 · Monitoring
Uptime Kuma, Prometheus, Grafana. Knowing when something is broken, before the family notices.
12 min read📖 Ch 08 · Home Automation
Home Assistant, MQTT, Zigbee, Z-Wave. The smart home that doesn't depend on the cloud.
12 min read📖 Ch 09 · When to Expand
Second machine, Proxmox cluster, dedicated hardware. The signs it's time.
10 min read📖 Ch 10 · Cloud Services
The cloud as part of the system. Cloudflare Tunnel, Backblaze B2, burst GPU. Hybrid done right.
14 min readThe "blast radius" principle
The single most important concept in this volume: the blast radius of a mistake. A mistake in the lab (a bad config, a destructive command, an experiment that goes wrong) should never take down the family's photos, videos, or documents. The way to ensure this is the data hierarchy from Volume 1: family data on one set of datasets, lab data on another. Snapshots and the discipline of testing in non-production.
What you'll know by the end
- How to set up a home lab that doesn't put the family data at risk
- How to use containers for self-hosted services
- How to use VMs for development and testing
- How to expose services to the internet securely with HTTPS
- How to know when something is broken before the family notices
- How to integrate the smart home with the home lab
- When to expand the lab to a second machine or a cluster
The home lab is for learning. Every sysadmin learned their craft by breaking things in a lab. The point of this volume is to give you a structured way to do that learning without breaking the family data. The lab should be a place for experiments, not a place where experiments happen to other people's stuff.