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.

  • Hutch
    link
    fedilink
    English
    32 years ago

    I use Ansible, Docker, and Emacs OrgMode files committed to Git. Diagrams are a mix of Miro and Graphviz. There’s also a few markdowns in there too. Joplin is used for rough notes only.

  • @NewDataEngineer@lemmy.world
    link
    fedilink
    English
    42 years ago

    I use trillium that gets backed up every hour to my pc.

    I also do a lot of python development so my project ideas get written down there too.

    I’m not a fan of code is documentation because what happens when you step away for a month and you need to figure something out? In trillium I have a search bar. What do you have in the code?

    • Human Crayon
      link
      fedilink
      English
      12 years ago

      I will second trilium. I use their sync server in a VM (which is backed up with the rest of my VM’s so its easy to drop back down should something happen). The app appeals to me, even after using Obisdian for the past 6 months (i’m a fan of markdown as well).

  • rentar42
    link
    fedilink
    32 years ago

    I know that I would keep forgetting to update the docs, so my documentation are the ansible playbooks and docker-compose.yaml files that I use to set it all up.

    That leaves anything that has to be done in some Ui undocumented, so I try to keep that to a minimum, which isn’t always easy (I’m looking at you authentik!).

    • Ideally I’d like to move in that direction. I have some Ansible roles that I use for initial configuration but I haven’t kept current. I’d like to get better about that as part of this project.

  • dr_robot
    link
    fedilink
    22 years ago

    I deploy as much as I possibly can via Ansible. Then the Ansible code serves as the documentation. I also keep the underlying OS the same on all machines to avoid different OS conventions. All my machines run Debian. The few things I cannot express in Ansible, such as network topology, I draw a diagram for in draw.io, but that’s it.

    Also, why not automate the certificate renewal with certbot? I have two reverse proxies and they renew their certificates themselves.

      • dr_robot
        link
        fedilink
        22 years ago

        Why not have the reverse proxy also do renewal for the SMTP relay certificate and just rsync it to the relay? For a while I had one of my proxies do all the renewals and the other would rsync it.

        • It certainly wouldn’t be because I’ve been doing it this way for so long that it never occurred to me. Nope. Certainly not that.

          In fairness, I very recently switched from a cobbled together apache web server/rev proxy config I’ve been carrying along in some form for well over a decade (I remember converting the config to 2.4), to an NPM container. I had some initial trouble switching my certs over to NPM and haven’t revisited that yet.

          I’m in the middle of a major overhaul of my tech stack. Fixing certs is on my short list.

          Thanks for pointing out where I was stuck in my ways.

  • @tuhriel@infosec.pub
    link
    fedilink
    English
    42 years ago

    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

    • Kurotora
      link
      fedilink
      English
      12 years ago

      +1 for bookstack. I also selfhost a kanban with the services basic info and it’s related status (pilot/test, production and to be decommissioned). At the beginning I used Planka, but now switched to Nextcloud Deck.

    • 𝙚𝙧𝙧𝙚
      link
      fedilink
      English
      22 years ago

      This is interesting. I already just keep a collection of markdown files… might as well make it an internal documentation site so it’s easier to browse 🤔

  • *dust.sys
    link
    fedilink
    English
    222 years ago

    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.

        • Deebster
          link
          fedilink
          English
          3
          edit-2
          2 years ago

          I love Mermaid, although I don’t think you can currently do network diagrams. I’ve seen Kroki recommended here for doing that, which supports Mermaid plus many similar markup-based diagrammers.

          [Edit: added link and more info]

          • @med@sh.itjust.works
            link
            fedilink
            English
            22 years ago

            I would not consider Mermaid complete enough for network diagramming. The very basics are possible, but try to describe anything more complicated throws off the placement and makes the pathing whacky.

            Straight flow charts are the closest you can get to a network diagram, so if you try to draw a link that travels back up the chart, it breaks mermaid’s brain trying to figure out the order of decision points (network devices).

            The allure of text based diagrams is so tantalizing - but if you need them to be functional, it’s not going to happen

            There’s an issue tracking the need a new diagram type to handle it.

          • Shertson
            link
            fedilink
            English
            22 years ago

            This is the first I’ve heard of Kroki. A quick glance at their site and wow! So many options for markup. I’ll be trying this out for sure

      • *dust.sys
        link
        fedilink
        English
        82 years ago

        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.

  • @Omripresent@leddit.social
    link
    fedilink
    English
    32 years ago

    I use a combination of netbox for the physical/logical network and server connectivity, and outline for text documentation of the different components.

  • @jackoneill@lemmy.world
    link
    fedilink
    English
    32 years ago

    I made myself a wiki in my helpdesk system - I use osticket to send me various email alerts to so I can track issues I need to fix, and they have a little wiki option.

    Then one day that host was down and I needed some info and I was very irritated. Now all of those notes are in my Apple notes backed up in iCloud and searchable on whatever I’ve got handy so if I need info I can get the info

    • 𝓢𝓮𝓮𝓙𝓪𝔂𝓔𝓶𝓶OP
      link
      fedilink
      English
      32 years ago

      I played with GLPI just long enough to realize that was way more than I wanted or needed. I’d like to track changes but I don’t want to run a full ticketing/chg mgmt system to do it.

    • @mholiv@lemmy.world
      link
      fedilink
      English
      72 years ago

      +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.

  • Szwendacz
    link
    fedilink
    52 years ago

    My config files are my documentation, but what is not suitable to be written in config files I write in selfhosted BookStack

  • poVoq
    link
    fedilink
    English
    52 years ago

    Mix of a Bookstack wiki and various git repos on my self-hosted Forgejo.