ποΈ The TK Home
Infrastructure Handbook
A living, continuously maintained knowledge base for TK's home lab β built one volume at a time, the same way we built the lab itself: incrementally, with understanding.
What this is
Not a TrueNAS manual. Not a one-off PDF. This is a living body of knowledge that grows alongside the lab. It started as a single question in a conversation with ChatGPT β "what's a pool?" β and grew into a multi-volume handbook covering storage, networking, virtualization, services, and the philosophy behind building infrastructure you can actually understand.
The website is the canonical version. PDFs are snapshots. The PRD (Product Requirements Document) is the constitution every chapter is measured against.
The 8 design principles
Every chapter, recommendation, and architectural decision in this handbook is measured against these principles. They were drafted in the original conversation with ChatGPT and are the spine of the project.
Structure
The handbook has three layers:
π The PRD
20 sections defining the mission, audience, writing standards, chapter template, and the complete volume roadmap. The constitution every chapter is measured against.
20 sections Β· the spineπ Volumes
Six volumes, each with its own chapters. Start with Volume 1 (Foundations) β drives, vdevs, pools, datasets, SMB, users, permissions. Build out from there.
6 volumes Β· 45 chaptersπΊοΈ Roadmap
What's done, what's in progress, what's coming next. The handbook is open-ended β new volumes get added as the lab evolves.
living planHow to use this site
- Read the PRD first β it defines the philosophy and standards every chapter follows.
- Start with Volume 1 if you're new to TrueNAS or ZFS. It builds the mental model before any commands.
- Use the sidebar search to find concepts across any page (page-level for now; site-wide search coming in Phase 2).
- Print any chapter to PDF using the "Save as PDF" button at the top. The print stylesheet strips nav and produces a clean, book-style export.
- Dark mode follows your system by default. Add
prefers-color-schemesupport to your reader if needed.
A guide is finite. A handbook is something you keep on the shelf and reach for again and again. Five years from now, when TK is running AI servers, a second NAS, and a Kubernetes lab, the handbook will still be relevant β because it documents the thinking, not just the buttons.