[1] https://github.com/dani-garcia/vaultwarden/wiki/Using-Docker...
Now - I used traefik and caddy extensively (and everything I do is in docker these days) and caddy is so much, much better than traefik.
I used traefik v1 and v2 and struggled with having an optimal configuration. With caddy it just works.
The main difference is that with traefik you usually try to squeeze your configuration in the docker-compose.yaml, but end up with a traefik configuration as well.
With caddy you have everything in a caddy file - in my case adding a service with plenty of things set up (filtering for networks etc. is a matter of adding
https://my-new-service.com { import lan container-name:PORT }
On top of that, the caddy community is great - some questions may seem simple for the ones who are used to proxies etc. but are very hard to understand for the newcomers. There are always kind guidance for these people in the forum.
It is truly excellent, especially the fact that you can "move" an entry to an organization, where everyone has the same ownership and rights (and not merely "share" it). Plus a ton of wonderful things.
There are two minor points I am missing:
- the ability to control someone's passwords. Typical usage: the 24/7/365 support for my parents, where I would like to be able to access their passwords (they also would like that, obviously). There would be a simple solution: the ability to force someone to file entries only in an organization. But it is not possible (and new entries will go to the personal vault by default).
- the ability to discard the Android pop-up, sometimes it completely blocks the ability to manually fill in something. An "escape" kind of gesture.