# How do you actually document your homelab in a way that survives your own memory failing you? — retained record

> Retained reddit record from reddit:homelab.

Canonical: https://highsignal.app/data/records/23a5dbec1aaa7b0e

[← sources](https://highsignal.app/data)


source: [reddit](https://highsignal.app/data/reddit) (reddit:homelab)  published 2026-09-18 14:09 ingested 2026-09-19 02:41

[original source ↗](https://www.reddit.com/r/homelab/comments/1wjr9z2/how_do_you_actually_document_your_homelab_in_a/)

## retained text



```
Three weeks ago I had to rebuild a VM I set up about six months back. I remembered roughly what I did but not the specifics, and I spent more time reverse engineering my own choices than I would have spent just starting from scratch with notes. That was the moment I realized my documentation situation is basically nonexistent.

At work there are runbooks, change logs, a ticketing system. None of that friction exists at home so nothing gets written down. I get something working, move on, and trust that future me will figure it out. Future me is not grateful for this.

The part I keep going back and forth on is the format. A wiki feels like overkill for a two node setup. Plain text files are easy to neglect. I've seen people mention Obsidian or Notion but I'm not sure either of those is the right fit when what I really want is something close to where the infrastructure actually lives.

The other thing I genuinely don't know is what level of detail is worth capturing. Do you document every config change or just the decisions that took you more than an hour to figure out? There's probably a middle ground but I haven't found it yet.

What does your homelab documentation actually look like in practice, not in theory?
```



document fetched 2026-09-19 00:35 · canonical https://reddit.com/r/homelab/comments/1wjr9z2/how_do_you_actually_document_your_homelab_in_a
