Hello, how do you document your home lab? Whether it’s a small server or a big one with firewall and more nodes. I have a small pc with Proxmox and there I have a VM with OpnSense. After I’ve entered my VPN as a interface in OpenSense, I noticed that I slowly lose the overview with the different rules that I have built in my firewall. And I know that my setup is relatively easy in comparison to others here in this community. I want to have a quick Overview at the various VMs, like the Lxc container, Docker containers that I have in this and the IP addresses that I have assigned to them. I search for a simple an intuitiv way for beginners.

  • fmstrat@lemmy.nowsci.comEnglish
    2·
    22 hours ago

    Every time I set up anything, I do one of two things:

    • If it’s container based, it gets a commented docker compose file in my custom orchestration

    • If it’s on a host system, the changes are scripted and commented in a setup script, which are run on new machines. If the acrit is specific to one machine, it is configured as such

    I find in-setup docs to be best for a home lab, plus if I have to replace hardware, it’s fast.

    Fun fact, I do it for laptops and desktops, too.

    • CapitalNumbers@lemm.eeEnglish
      2·
      11 hours ago

      this is basically what i ended up doing to - glad to see my approach verified somewhat ha ha!

      but yeah, in general whenever i make a change / add new service, i always try and add those steps to some sort of setup.sh / docker-compose

      • fmstrat@lemmy.nowsci.comEnglish
        1·
        9 hours ago

        Yea comes in super handy when you always want dropbear SSH for remote unlock, or making sure both RAID disks boot, etc.

        I do it for all my software setup, too. A shell script for each, then a for loop that asks to run each. But I also made https://github.com/fmstrat/gam, so maybe I just like overkill bash.