Ever wondered how to use Traefik as a Reverse Proxy? I wrote a simple Guide for beginners.

I wrote a guide for traefik v2 with a simple WordPress docker-compose.yml example.

I hope the instructions can help someone who, like me, was a little lost at first configuring Traefik correctly.

[https://ae3.ch/install-use-traefik-reverse-proxy-docker](https://ae3.ch/install-use-traefik-reverse-proxy-docker)

5 thoughts on “Ever wondered how to use Traefik as a Reverse Proxy? I wrote a simple Guide for beginners.”

  1. Super timely my friend, I have wanted to do this and started to take a look at the docs a couple of times but hadn’t been able to find something like this. Thanks for sharing!

    Reply
  2. You should consider *not* putting your config in the compose files, and instead have a config directory with files for each container/stack. Certainly in production or as your setup grows.

    It’s not as convenient sometimes, but it means you don’t have to recreate a whole container when you change network settings. It also means you can quickly change ports for services, and do quick changeovers between containers (for example where you stand up a new version in a new container, and want the old ones running for zero downtime) accessible on specific ports.

    A bonus is that, since networking tends to be implementation-specific, your compose files stay portable.

    Reply
  3. Aw jeez.
    Caddy config is two lines per reverse proxy, with less setup overall.

    Why would you do this ? Are there any benefits to having reverse proxy managed over docker socket ?

    Reply

Leave a Comment