This is a traefik setup template you to setup a a reverse-proxy for all your docker containers
Traefik is based on the concept of EntryPoints, Routers, Middlewares and Services.
- EntryPoints: are the network entry points into Traefik. They define the port which will receive the packets, and whether to listen for TCP or UDP.
- Routers: is in charge of connecting incoming requests to the services that can handle them.
- Middlewares: Attached to the routers, middlewares can modify the requests or responses before they are sent to your service
- Services: are responsible for configuring how to reach the actual services that will eventually handle the incoming requests.
You can configure Traefik in two ways:
-
The fully dynamic routing configuration (referred to as the dynamic configuration)
- The dynamic configuration contains everything that defines how the requests are handled by your system. This configuration can change and is seamlessly hot-reloaded, without any request interruption or connection loss.
foo@bar:~$ vim /data/config.yml
-
The startup configuration (referred to as the static configuration)
- Elements in the static configuration set up connections to providers and define the entrypoints Traefik will listen to (these elements don't change often).
foo@bar:~$ vim /data/traefik.yml
- Create a docker network
foo@bar:~$ docker network create proxy-network-name- Change host name to your domaine name
rule=Host(`traefik.yourdomaine.com`)"
- If you are planning on using letsencrypt as your certificatesResolvers change the email to your email
email: your-email@example.com
- Switch to the caServer for production
caServer: "https://acme-staging-v02.api.letsencrypt.org/directory" # for testing
caServer: "https://acme-v02.api.letsencrypt.org/directory" # for production
- Create your Traefik Dashboard username and password using htpasswd
foo@bar:$ sudo apt install apache2-utils
foo@bar:$ htpasswd -nb username password
username:$encrypted/password