My home lab has a mild amount of complexity and I’d like practice some good habits about documenting it. Stuff like, what each system does, the OS, any notable software installed and, most importantly, any documentation around configuration or troubleshooting.
i.e. I have an internal SMTP relay that uses a letsencrypt SSL cert that I need to use the DNS challenge to renew. I’ve got the steps around that sitting in a Google Doc. I’ve got a couple more google docs like that.
I don’t want to get super complicated but I’d like something a bit more structured than a folder full of google docs. I’d also like to pull it in-house.
Thanks
Edit: I appreciate all the feedback I’ve gotten on this post so far. There have been a lot of tools suggested and some great discussion about methods. This will probably be my weekend now.
Well, whatever you end up using for documentation, print it out and actively maintain an up to date paper hard copy in a 3-ring binder somewhere. That way when all your shit falls over and you have a nonfunctional LAN you can still remember how everything was set up. Don’t ask me how I know…
Documentation is not worth much if you can’t access it when needed. So yes, either print it out or store it somewhere else what you can access even if your own hardware is completely dead.
+1 for hard copy. Hang/tape right on or next to the rack.
deleted by creator
I’ve been using Obsidian for a lot of other purposes for a couple years now, so I was comfortable adding my documentation into my existing vault there. I made a couple templates that I fill out for any hardware/software/networking equipment.
Since the app’s selling point is storing all your notes in plain text I wouldn’t put anything security-related in there without some encrypted container. I use KeePass for that part, and keep the file it generates in the same folder as Obsidian so I can link to it within notes. Click the link in the note, KeePass opens the vault and asks for its password.
Mind sharing your template?
Sure.
I left everything in, so no doubt there’s stuff in there specific to my vault you won’t need like metadata - adjust these to your needs or use them as a starting point for something new. There’s no network device template, I usually use the hardware one and just delete the irrelevant bits.
Thanks!
I use obsidian too. It supports mermaid too so you can make your network diagram with it.
This is the 2nd ref I’ve seen to mermaid. I need to check that out.
Everything is containerized, so i just have a yaml file with all the information i need to rebuild each container. Easy! Has come in handy a few times.
I use WikiJS for documentation. Simple, powerful and has a lot of features
+1 for WikiJS. As a bonus you can have WikiJS back itself up to plain text MarkDown files, so if things explode you can always just read those from wherever.
Another great feature I use is to have WikiJS back itself up into git. If I am going to a place with no internet access I can do a quick git pull and have a complete copy of my wiki including files on my laptop.
That sounds pretty handy.
Git, MinIO, Amazon S3, Filesystem and many more options to for backup🐱
Can’t wait for v3 finally
Joplin has been my note-taking app of choice. Free (OSS); no accounts needed; simple; local; synchronizes through my Nextcloud instance to Linux, Windows and Android; markdown-based, etc. It’s been a good workflow for me and makes taking and searching through notes quick and pretty painless.
I document my setup, backup and restoration procedures (done rarely enough that it’s good to have it written down), etc. with it.
+1 for Joplin. I have a different setup since I don’t use Nextcloud: Run Joplin server in a docker container and back up the volumes mapped to it (as well as those of other containers) with rsync.
Mine is, er, self-documenting, and my partner has instructions, in the event that I die, to plug the wifi router into the modem and unplug all the other crap. The router has a sticker saying ROUTER and the modem has a sticker saying MODEM.
Self documenting, eh? I may be familiar with the same process.
You just follow all the wires and read all the config files. Easy!
As I move to more self hosting, it’s becoming more and more important to create a “what to do if I die” procedure for my wife (or even children) to follow. I mean it’s not big deal if the plex server goes down and doesn’t come back up, I’m thinking more along the lines of all of our photos, important documents, password manager, those type of things. I have 3 - 2 - 1 backups for the important stuff and have tested them, but that means nothing to my wife if I wasn’t around to get that stuff back if something happened… I wonder some days if I should document it all and put a print out with a step by step guide on how to get everything back that a semi tech savvy person could follow.
Yes, I really need to do this too. It’s a fairly daunting task because my significant other is not at all comfortable with even slightly complicated operations on a computer. I need to figure out a way to make a really easily accessible backup of everything.
ansible, self-documenting. My
playbook.ymlhas a list of roles attached to each host, each host’shost_varsfile has details on service configuration (domains, etc). It looks like this: https://pastebin.com/6b2Lb0MgAdditionally this role generates a markdown summary of the whole setup and inserts it into my infra’s
README.md.Manually generated diagrams, odd manual maintenance procedures and other semi-related stuff get their own sections in the README (you can check the template here) or linked markdown files. Ongoing problems/research goes into the infra gitea project’s issues.
I’m only just starting to dip my toes in docker. Most of my stuff are kvm vms. I have a decent set of Ansible roles to setup a new vm when I spin it up but I’m not to the point where the specifics of every system is in Ansible yet.
You can full well deploy docker stacks using ansible. This is what I used to do for rocket.chat: [1] [2] (ditched it for Matrix/element without Docker, but the concept stays valid)
I’m not to the point where the specifics of every system is in Ansible yet.
What I suggest is writing a playbook that list the roles attached to your servers, even if the roles actually do nothing:
# playbook.yml - hosts: myhomeserver.example.org roles: - debian-base - docker - application-x - service-y - hosts: mydevserver.example.org - debian-base - application-z# roles/application-x/tasks/main.yml - name: setup application-x debug: msg: "TODO This will one day deploy application-x. For now the setup is entirely manual and documented in roles/application-x/README.md"# roles/application-x/tasks/main.yml - name: setup service-y debug: msg: "TODO This will one day deploy service-y. For now the setup is entirely manual and documented in roles/service-y/README.md" #...This is a good start for a config management/automated deployment system. At least you will have an inventory of hosts and what’s running on them. Work your way from there, over time progressively convert your manual install/configuration steps to automated procedures. There are a few steps that even I didn’t automate (like configuring LDAP authentication for Nextcloud), but they are documented in the relevant role README [3]
That makes a lot of sense.
I was going to recommend Ansible as well - documentation as code can never be out of date if you continue using it.
I run wiki.js for documentation for my home lab, but also things like the custom rom setup for my phone. However it’s hard to keep it up to date as I forget it exists. I mostly use it to document setting up windows server core with different roles as I don’t need to do that often, but most tutorials on the web are SEO optimised with low quality
Mix of a Bookstack wiki and various git repos on my self-hosted Forgejo.
I’m not very good at deciding on where to document things, so I have a mix of BookStack, Dokuwiki, and Obsidian currently.
I really like Dokuwiki but I like the UI/UX of BookStack better so I’m working on a plugin to sync bookstack and obsidian. I’ll probably get rid of Dokuwiki after that.
The main reason for syncing with obsidian is that I want documentation that isn’t stored on the thing it’s about, in case my servers completely die.
In another thread, someone reminded me that TiddlyWiki still exists, it’s also a pretty cool little tool.
Obsidian. I love that it uses simple markdown files so it’s platform agnostic. Documenting my setup has been a lifesaver.
Syncthing plays nicely with obsidian if you ever have to synchronise the vault between multiple devices.
That too. Sometimes that is, if I bother with documenting at all.
Almost nothing haha. Some half-ass notes saved here and there, in a disorganized manner.
My stuff works, but I don’t recommend my approach.
This is what I’m trying to get away from.
Same, my stuff continuing to work relies on thoughts and prayers.
I was going to say my notes are in Joplin, but my more honest answer is basically yours.
Same, but I have no plan to change. My setup isn’t very complex so there’s not much to track. Most of it is just one docker compose file. It would just be one more thing to maintain without much benefit.
This is the way.
I’m using netbox, and I’m in the process of info dumping my brain to a media wiki. I may add ansible into the mix in the near future.
My lab is a bit large and complex and I’m currently in the process of trying to train help to run it, from the pool of people that make use of it. They know how the front end works, a few of them need to learn the back end.
Ibrun my own gitlab instance where i have a repository with all my configs, scripts etc.
As well as a wiki that contains the admin guide with (hopefully) all the relevant infos in form of text and PlantUML graphs.The nice thing is… You can just ‘code’ the diagrams and use a PlantUML instance to render the graphs live
Thoughts and Prayers.
The real enterprise solution.
