bitwarden_rs VS caddy-docker-proxy

org.opencontainers.image.documentationhttps://github.com/dani-garcia/bitwarden_rs/wiki

Bitwarden (Not officialy version), A password manager, provides browser extensions and clients on all platforms.

- use trusted images (for bitwarden i'm using bitwarden_rs , an unofficial Bitwarden server implementation written in Rust

https://github.com/dani-garcia/bitwarden_rs/issues/246#issuecomment-796966385

Bitwarden-rs

Bitwarden RS (https://github.com/dani-garcia/bitwarden_rs) running as addon in Home Assistant (Docker)

I have setup Bitwarden on my raspberry following Bitwarden_RS (https://github.com/dani-garcia/bitwarden_rs/wiki )using portainer docker manager instead of command line and setup frp server to connect my apps including Bitwarden which is hosted in my lan from internet

If you're okay with a third party solution, bitwarden_rs is a much lighter version of bitwarden that can run in docker

I have some loaded into my self-hosted Bitwarden RS, but that's definitely not my primary.

https://github.com/lucaslorentz/caddy-docker-proxy

It handles the routing to multiple dockerized projects on one server, by scanning docker compose files for labels and automatically setting up the required caddy configuration.

My go to is always this instead:

https://github.com/lucaslorentz/caddy-docker-proxy

Single label to a docker container and with correct DNS you’ll have an automatically managed certificate right away.

I have had a great experience with using this: https://github.com/lucaslorentz/caddy-docker-proxy

It combines caddy with docker-compose labels, making it super easy to spin up new projects that can immediately be exposed.

If you want a slightly heavier but more robust solution, caddy-docker-proxy[0] is a plugin that listens to the Docker socket and automatically updates the Caddy configuration based on Docker labels you add to containers.

I.e. it makes Caddy act a bit more like Traefik. Most of the time, you'll just add the label `caddy.reverse_proxy={{upstreams http 8080}}` to your containers and the plugin will regenerate Caddy's configuration whenever the container is modified.

[0] https://github.com/lucaslorentz/caddy-docker-proxy

I disagree, Caddy works great in Docker. See https://caddyserver.com/docs/running#docker-compose, and CDP is a project that autoconfigures Caddy from labels https://github.com/lucaslorentz/caddy-docker-proxy. Regarding plugins, it's super simple to write a Dockerfile to add plugins, we ship a builder image variant that can be used to compile in any plugins you want.

````

This way, Caddy will buffer the request and give 30 seconds for your new service to get online when you're deploying a new version.

Ideally, during deployment of a new version the new version should go live and healthy before caddy starts using it (and kills the old container). I've looked at https://github.com/Wowu/docker-rollout and https://github.com/lucaslorentz/caddy-docker-proxy but haven't had time to prioritize it yet.

Docker labels support is available via a plugin https://github.com/lucaslorentz/caddy-docker-proxy

Or caddy-docker-proxy: https://github.com/lucaslorentz/caddy-docker-proxy

I am trying now for some Days to use a Caddyfile additionaly to the auto generated files from lucas lorentzes caddy repositroy. https://github.com/lucaslorentz/caddy-docker-proxy