Reading earlier comments in this community made me consider documenting the workings of my homelab to some extent, ie. docker configuration, credentials, ports and links of my services. I’ve tried to make it consistent and organised but it still feels half baked and insufficient. Everyone suggests documenting everything you do in your homelab but don’t state how. Since I’ve hardly had experience running my own server, I would really appreciate observing the blueprint of some other fellow selfhoster for copying or taking inspiration from rather than considering documentation to be ‘left as an exercise for the reader’.
Edit: I already have a note-taking solution with me. What I wish to ask is to know what needs to be documented and what the structure of the documentation should be to accommodate the information.
Everyone will have their own system.
I save all my credentials in Bitwarden/Vaultwarden and take notes in Joplin.
The good thing about YOUR homelab is that YOU’RE taking notes solely for YOURSELF and only YOU know how YOU work and how YOU organize YOUR thoughts.
Normally I’d agree, in that it’s not some corporate production environment, but also I personally want to document my self hosted setup in a kind of document that can at least be accessed and understood by my closest family, if something were to happen to me.
Convincing them to archive stuff on my Nextcloud instance for example, and them losing access because I’m not around, temporarily or permanently, would spoil the whole point of the endeavor.
I‘m a realist in that regard, once I am gone all my hard work will go to shit in 6-12 months no matter how much I train an instruct my friends and family. They just don’t care enough to put in even a little bit of work.
Yeah, I don’t put key phrases, passwords, etc in my notes.