1. Less dependencies (only Podman and registry is needed)
2. Rock solid rootless systemd service management
3. Easy integration with systemd-proxyd
4. Easy manage dependencies between containers (with healthchecks)
5. Rollbacks
Sounds interesting! Is there any support for multi-node systems? Let's say I want to have an ingress Caddy proxy on one node, which reverse proxies to several backed APIs on other nodes - can this be done simply with Podman Quadlet?
Also, what is the localdev UX like? With Docker Swarm I can easily run very similar setups in dev, test and prod, and it works with multi-node setups, has support for secrets etc. But the lack of work going into Docker Swarm becomes more concerning as the years pass by.
Also, had no idea systemd-proxy was a thing - is there anything systemd doesn't have its tentacles into? :)
If your VPS is wired with another one using VPC or any other internal network it'll just work. Just point Caddy to specified internal IPs of your other servers.
It's not designed to work on local envs. When I wanted to debug infra I used to run it on Vagrant though
