Use env variables

[danielo515]

Hello.
I think it will be a lot easier to reuse the templase if you just use env variables rather than text placeholders. You can even include an example .env file where you just have to put all the configurations variables and then use that env file on the docker compose which in turn will pass it down to traefik and all the services.

What do you think?

[timothystewart6]

Hey, sounds good!

[danielo515]

Cool.
As an example, this is what I ended with after editing your base files. This is the docker-compose for traefik:

version: '3'

services:
  traefik:
    image: traefik:latest
    container_name: traefik
    restart: unless-stopped
    security_opt:
      - no-new-privileges:true
    networks:
      - proxy
    ports:
      - 80:80
      - 443:443
    environment:
      - CF_API_EMAIL=${CF_API_EMAIL}
      - CF_DNS_API_TOKEN=${CF_DNS_API_TOKEN}
      - DOMAIN=${DOMAIN}
      # - CF_API_KEY=YOU_API_KEY
      # be sure to use the correct one depending on if you are using a token or key
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - /var/run/docker.sock:/var/run/docker.sock:ro
      - ./data/traefik.yml:/traefik.yml:ro
      - ./data/acme.json:/acme.json
      - ./data/config.yml:/config.yml:ro
    labels:
      - "traefik.enable=true"
      - "traefik.http.routers.traefik.entrypoints=http"
      - "traefik.http.routers.traefik.rule=Host(`traefik-dashboard.${DOMAIN}`)"
      - "traefik.http.middlewares.traefik-auth.basicauth.users=${BASIC_USER}:${BASIC_AUTH}"
      - "traefik.http.middlewares.traefik-https-redirect.redirectscheme.scheme=https"
      - "traefik.http.middlewares.sslheader.headers.customrequestheaders.X-Forwarded-Proto=https"
      - "traefik.http.routers.traefik.middlewares=traefik-https-redirect"
      - "traefik.http.routers.traefik-secure.entrypoints=https"
      - "traefik.http.routers.traefik-secure.rule=Host(`traefik-dashboard.${DOMAIN}`)"
      - "traefik.http.routers.traefik-secure.middlewares=traefik-auth"
      - "traefik.http.routers.traefik-secure.tls=true"
      - "traefik.http.routers.traefik-secure.tls.certresolver=cloudflare"
      - "traefik.http.routers.traefik-secure.tls.domains[0].main=${DOMAIN}"
      - "traefik.http.routers.traefik-secure.tls.domains[0].sans=*.${DOMAIN}"
      - "traefik.http.routers.traefik-secure.service=api@internal"

networks:
  proxy:
    external: true

And this is the example .env file:

DOMAIN=example.com
TZ=Europe/Madrid
BASIC_USER=nobody
BASIC_AUTH='use generate-auth.sh but remove escaping'
CF_DNS_API_TOKEN=your_api_token
CF_API_EMAIL=nobody@gmail.com

The reason I am also passing some environment: variables to the container is because I also edited the configuration files to use env variables like this:

http:
 #region routers 
  routers:
    proxmox:
      entryPoints:
        - "https"
      rule: 'Host(`proxmox.{{env "DOMAIN" }}`)'
      middlewares:
        - default-headers
        - https-redirectscheme
      tls: {}
      service: proxmox

What do you think? Do you like it? For now, I have a .env file linked on each subfolder, so I don't have to edit several files. If you know any other better way to pass multiple env variables, I'm open to it.

[timothystewart6]

Thanks for the example! I'd love to update them at some point, I will probably start with https://github.com/techno-tim/launchpad and update the associated blog post at the same time. I too use .env but wasn't sure how prescriptive I should be for demos. Will work through these are some point!