Comment on How do you document your Homelab?
fmstrat@lemmy.nowsci.com 2 weeks 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.ee 2 weeks 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.com 2 weeks 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 github.com/fmstrat/gam, so maybe I just like overkill bash.