This is an automated archive made by the Lemmit Bot.
The original was posted on /r/selfhosted by /u/bytesfortea on 2025-07-27 09:46:52+00:00.
Hello fellow community,
I guess this has been discussed before but I couldn't find the ultimate solution yet.
My # of selfhosted services continues to grow and as backup up the data to a central NAS is one thing, creating a reproducible configuration to quickly rebuild your server when a box dies is another.
How do you Guys do that? I run a number of mini PCs on Debian which basically host docker containers.
What I would like to build is a central configuration repository of my compose files and other configuration data and then turn this farm of mini PCs into something which is easily manageable in case of a hardware fault. Ideally when one system brakes (or I want to replace it for any other reason), I would like to setup the latest debian (based on a predefined configuration), integrate it into my deployment system, push a button and all services should be back up after a while.
Is komodo good for that? Anyone using it for that or anything better?
And then - what happens when the komodo server crashes?
I thought about building a cluster with k8s/k0s but I am afraid of adding to much complexity.
Any thoughts? TIA!