Like soup-to-nuts. I know I need to document what I’m doing and I’ve started several times, but then I never go back and make updates. I don’t know if it’s just the ADHD or if I’m just going about it or thinking about it in the wrong way.

So I’m curious about:

  • what you use for your documentation
  • how you organize it
  • what information you include
  • how you work documentation into your changes/tinkering flow

Edit: Dang, folks! You all have given me a lot to read through, think about, and explore. Thank you!

  • bizdelnick@lemmy.mlEnglish
    0·
    7 hours ago

    you don’t really need to scale a homelab that much

    Maybe. But you never know this beforehand.

    if something breaks, you just want to quickly fix it manually because “doing the Ansible” is more of a pain

    In most cases you just need to replay a playbook for quick fix. But I agree that the proper fix will likely take a longer time (while downtime is much shorter).

    now idempotency and documentation-as-code is out of the window.

    Let @BruisedMoose@piefed.social decide.

    P. S. I don’t like Ansible, other tools can be easier to use. But I don’t want to recommend something concrete.