Greetings Lemmings,

I realize that self-hosting for many is just a hobby. Something they do for fun. And the topic of today is usually a “not-so-fun” part of the IT industry.

Jump Scare Warning

Documentation

I have for so long just let my lab grow organically. And months down the road an issue pops up with a service, and I have no idea how I set something up, and may not have documented it. Whether that be comments inside of configuration files, or via other means.

I have gotten marginally better at documenting within the config files or code that I am writing. However, I don’t want just that as an option. So I spun myself up a Bookstack container.

I am slowly going through and creating what would amount to a full blown wiki for my setup. Doubly I can use this as part of my resume.

So I ask of you; what ways do you prefer to document? How do you keep yourself honest, and actually stick to it.

Edit: I created bash scripts that are run by a systemd service and timer. At least for my docker box.

  • emaginEnglish
    3·
    18 hours ago

    Obsidian - everthing goes into OBS (PKB) Claude MCP - I have claude interact with my .md files

    • Everytime Claude guides me thru an update or debug, I have it update the doc with a summary and details, including code snippets
    • Larger .yml files, etc. live in editable files attached to an OBS note

    Documentation is essential, not because it’s anal, but because it’s the framework to hand off to your favorite LLM (local or not) Put in your Goals, desired outcomes, etc. and LLM picks it all up prior to starting a session.

    There are other lighter PKBs than Obsidian, I just think it’s the standard. But anything will do Make sure it allows for [[Note-about-docker]] linking across notes My notes are crazy interlinked, each stack, service, UFW detail all links across the larger homlab ecosystem. No note sits alone - they all reference each other constantly The AIs love that stuff! Makes your life easier