SamAlvi said:
Seventeen routers and I can tell you which three I actually remember
This. I just counted and I have 31 services in my compose stack. I could explain maybe 8 to someone else. The rest are muscle memory and fear of touching them.
What do you use for documenting your network that you'll actually maintain?
Has anyone tried just... not having a complex network? I know that's not the forum demographic but my documentation got maintainable when I deleted half my VLANs and consolidated. Less to document, less to break, less to forget.
I went the opposite direction and automated the documentation. Python script walks my router configs, dumps to markdown, commits to git. It's stale within a week because I don't run it, and when I do run it the diffs are unreadable. Automation isn't the answer if you don't automate the automation.
This was covered in the first few replies but I'll add: the only living doc I have is my Pi-hole's local DNS records. If I need to remember what runs on port 8123, I look there. It's documentation by necessity because without it, nothing resolves.
YuriDavid
Member
red9 said:
Documentation by necessity
This is the actual answer. Documentation lives where the system dies without it. Everything else is vanity. My DNS zone files are pristine. My "architecture overview" is a 404.
indentation is not optional