I have a few options to set-up my personal journal and I intend to journal my process of how to, what’s the practical way of writing it all down with writing everything down ?
That’s the neat part, you don’t
Infrastructure as code, the code that is your homelab should be the documentation of it.
Infrastructure as code
Just some scripts and config files in external git at the moment but usually I just get my refrence form other VMs. Probably going with obsidian or other markdown editor and upload notes to somewhere if disaster strikes.
https://silverbullet.md/ and I may start using https://d2lang.com/ too.
Mkdocs, grav
Logseq
I blog it. https://static.xtremeownage.com/
Read it(pun intended), it was cool.
Obsidian with it’s folders/files in a location that gets duplicated to another drive by rsync.
Bookstack (/r/BookStack)
self hosted git repository.
I setup gitea on my server and use it to track version changes of all my scripts.
And I use a combination of the wiki and .md (readme) files for howto’s and any inventory I’m keeping, like IP addresses, CPU assignments etc.
But mainly it’s all in .md formatted with markdown.
Poorly.
Document?
About 2 years ago I came to the conclusion that my personal documentation for tech stuff is non existent. Some excel sheet here, a saved TXT in c:\temp over there, the occasional “I still need tot rewrite and save this unsaved file in Notepad++” combined with a bunch of google keep notes.
I ended up installing Wordpress with https://basepresskb.com/docs/knowledge-base/basepress/
I use it for virtually everything. From documenting the build of a server to simply logging expensive household equipment with extended warranty.I keep everything in my brain.
Has its perks… no need to write things down.
But it’s easy to momentarily forget the little things that come with, say, reinstalling everything.
I intend to be like that every time but now it’s getting a little overwhelming.