Skip to content

Latest commit

 

History

History
104 lines (80 loc) · 2.61 KB

Readme.md

File metadata and controls

104 lines (80 loc) · 2.61 KB
Raw

caddy-proxy

caddy-proxy automatically generates Caddy reverse proxy configurations for docker containers like jwilder/nginx-proxy for Nginx.

Usage

The template generation only works with docker-compose file version 2.

First, you'll need to create an external docker network named 'caddy-proxy'.

$ docker network create -d bridge caddy-proxy

Then Clone this repository.

$ git clone https://github.com/drlogout/caddy-proxy
$ cd caddy-proxy

Set a proper email address for LETSENCRYPT_EMAIL in caddy/docker-compose.yml.

version: "2"

networks:
  proxy-tier:
    external:
      name: caddy-proxy

services:
  caddy:
    container_name: caddy
    image: drlogout/caddy:0.9.5
    # remove -ca=https://acme-staging.api.letsencrypt.org/directory in production
    command: --conf /etc/caddy/config/Caddyfile --log stdout -ca=https://acme-staging.api.letsencrypt.org/directory
    ports:
      - 80:80
      - 443:443
    volumes:
      - "../volumes/config:/etc/caddy/config"
      - "../volumes/certs:/etc/caddy/certs"
    environment:
      - CADDYPATH=/etc/caddy/certs
    networks:
      - proxy-tier
    restart: always

  caddy-gen:
    container_name: caddy-gen
    image: jwilder/docker-gen:0.7.3
    volumes:
      - "/var/run/docker.sock:/tmp/docker.sock:ro"
      - "../volumes/templates:/etc/docker-gen/templates:ro"
    volumes_from:
      - caddy
    environment:
      LETSENCRYPT_EMAIL: "<YOUR EMAIL>"
    command: -notify "docker restart caddy" -watch -wait 5s:30s /etc/docker-gen/templates/caddy.tmpl /etc/caddy/config/Caddyfile
    restart: always

And start the caddy and caddy-gen containers.

$ cd caddy
$ docker-compose up -d

Then set the VIRTUAL_HOST variable to a fully qualified domain name in app1/docker-compose.yml (resp. in app2/docker-compose.yml).

version: "2"

networks:
  proxy-tier:
    external:
      name: caddy-proxy

services:
  app1:
    container_name: app1
    image: httpd
    networks:
      - proxy-tier
    environment:
      VIRTUAL_HOST: "<YOUR FQDN>"
      VIRTUAL_NETWORK: "caddy-proxy"
      VIRTUAL_PORT: 80
    restart: always

And start the app1 container (resp. app2).

$ cd ../app1
$ docker-compose up -d

Please note, that this caddy configuration uses the Letsencrypt staging environment. This means your browser will warn you about an insecure connection. For use in production remove the -ca=https://acme-staging.api.letsencrypt.org/directory flag in caddy/docker-compose.yaml.