Reading earlier comments in this community made me consider documenting the workings of my homelab to some extent, ie. docker configuration, credentials, ports and links of my services. I’ve tried it to make it consistent and organised but it still feels half baked and insufficient. Everyone suggests documenting everything you do in your homelab but don’t state how. Since I’ve hardly had experience running my own server, I would really appreciate observing the blueprint of some other fellow selfhoster for copying or taking inspiration from rather than considering the note taking to be ‘left as an exercise for the reader’.

  • fruitycoder@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    8
    ·
    2 months ago

    This is what I like about git ops and infra/config as Code personally.

    Ideally everything is an a tofu/ansible/helm chart and git lab pipeline/Fleet job. I add comments for anything that I had to learn to make work to those files. Follow good commit hygenine (most of the time). And bam I can almost a year later half asleep stumble back into a thing I did.

      • fruitycoder@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        1
        ·
        2 months ago

        Yep! Metal3 for servers with BMCs Tinkerbell for everything else.

        I also have an ansible playbook that templates everything into a cloud init scripts as a boot strap server.

        About 12 nodes in total now, from new servers to freebee junk laptops in it.