4 ms·

Docker-compose and be done with it. Kubernetes and NixOS are great and more powerful than docker compose, but the learning curve is longer. Feel free to graduat

Docker-compose and be done with it. Kubernetes and NixOS are great and more powerful than docker compose, but the learning curve is longer. Feel free to graduate to k8s or NixOS, once you are up and running with compose. Docker compose has the most tutorials, YouTube videos, the widest support among projects you want to self host, and many more people who can readily advise you on troubleshooting. Check out r/selfhosted to get a feeling. You can use portainer if you need a GUI but command line is not that complicated if you are comfortable with CLIs.

BrandoElFollito 3y ago
I completely agree. I did a disaster recovery test of my services (all on docker) from scratch and without documentation. I started by downloading the Debian ISO and went from there. It took me about 60 minutes to be up and running, this includes DHCP from pihole and getting everything from borg backups. I took notes to be faster/better next time but I lost them somehow :-| Docker everything and you will be fine. I used docker compose for years and recently moved to portainer because it is easier to keep track of the docker compose files and you have a lot of things readily available
- theshrike79 2y ago
  I have “runbooks” for all my servers and software in Obsidian. Every time I bootstrap it, I go through the instructions I wrote and improve/update if necessary. Much simpler than Ansible
  - BrandoElFollito 2y ago
    My last test was pre-Obsidian time (now I put everything in there). I will have to run one more time and, this time, make sure the steps are saved somewhere. Since I basically install the OS, configure networking, install docker, install borg, recover from backup, start portainer, start the stacks - it would be overkill to use Ansible for that (not to mention hat I am not a big fan of Ansible after having tried for a year to make it reliably work on lossy/unstable networks -- IMHO salt is much better)
meonkeys 3y ago
+1 to all these recommendations, and the ordering in terms of (time/money) investment, inclination, and synergy with projects at work. Compose is just the right fit for a small to medium setup and a great place to start.

BrandoElFollito 3y ago

I completely agree. I did a disaster recovery test of my services (all on docker) from scratch and without documentation. I started by downloading the Debian ISO and went from there. It took me about 60 minutes to be up and running, this includes DHCP from pihole and getting everything from borg backups. I took notes to be faster/better next time but I lost them somehow :-| Docker everything and you will be fine. I used docker compose for years and recently moved to portainer because it is easier to keep track of the docker compose files and you have a lot of things readily available

theshrike79 2y ago
I have “runbooks” for all my servers and software in Obsidian. Every time I bootstrap it, I go through the instructions I wrote and improve/update if necessary. Much simpler than Ansible
- BrandoElFollito 2y ago
  My last test was pre-Obsidian time (now I put everything in there). I will have to run one more time and, this time, make sure the steps are saved somewhere. Since I basically install the OS, configure networking, install docker, install borg, recover from backup, start portainer, start the stacks - it would be overkill to use Ansible for that (not to mention hat I am not a big fan of Ansible after having tried for a year to make it reliably work on lossy/unstable networks -- IMHO salt is much better)

meonkeys 3y ago

+1 to all these recommendations, and the ordering in terms of (time/money) investment, inclination, and synergy with projects at work. Compose is just the right fit for a small to medium setup and a great place to start.