3 ms·
I'm very happy using docker swarm on a single host with traefik as reverse proxy using the setup described here: https://dockerswarm.rocks/ https://dockerswarm.
by raphinou 5mo ago
I'm very happy using docker swarm on a single host with traefik as reverse proxy using the setup described here: https://dockerswarm.rocks/ https://dockerswarm.rocks/
Super easy deployment of additional apps, defined completely in one file (incl setup on host, backups, reverse proxy config, etc).
Never found a reason to migrate away. Swarm was already considered dead when I started using it in 2022[1], but the investment was so low and benefits so big, that it was the right choice for me. I think a lot of people are replicating swarm features with compose, losing a lot of time. But hey, to each their own choice!
1: https://www.yvesdennels.com/posts/docker-swarm-in-2022/ https://www.yvesdennels.com/posts/docker-swarm-in-2022/
- QGQBGdeZREunxLe 5mo agoSwarm or Nomad is the way to go for simple single/multi-node setups. https://developer.hashicorp.com/nomad https://developer.hashicorp.com/nomad Disclaimer: I used to work for HashiCorp
- time4tea 5mo agoYup, this works so nice. Using traefik or caddy as proxy. Docker context for remote access - over Internet or vpn, whatever. Swarm-cronjob for scheduled things. Labels for things that need to run in particular places. So easy. Personally, k8s is fine, but its an abstraction for building a service architecture, not the thing an end user (developer) should ever use. If you are in a big company and you are using helm or k8s yaml files to roll things out, your infra or platform teams have missed something out.. building the platform!