Traefik-v2-examples VS caddy-docker-proxy

Theres also traefik guide but the contrast in complexity is apparent right away.

Traefik that I tried first is very powerful but there are few abstraction layers and bit of complexity that I felt like I had to re-learn it every time I was about to do a change. But it is very powerful in dynamic enviroments where one spins often enough more new containers.

My first reverse proxy was traefik, but it was just too complex, with too many abstraction layers for my use. I needed to re-learn it every time I went to make changes.

I tried traefik. As I was learning it, which was like a week or two of effort, I actually wrote a guide that somehow got 500 stars on github...

Theres also traefik, that people recommend, but IMO for home stuff it is too complex with too many abstractions. Caddy is literally just giving it port 80 and 443 and a single clean config file.

Traefik is actuall business aimed and powerful and probably worth learning if you would need to manage lot of containers and change stuff dynamically on the fly. But it is just so damn complicated and you kinda need to re-learn it every time you return to it. Here is guide for that one..

You can try look here

Here is a decent guide that gets you going.

Have you considered going caddy instead of traefik?

How to reverse proxy with traefik

Caddy via Caddy Docker Proxy (network).

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