Watchtower deploys

Schedule for automatic updates

On weekdays between 9:00 and 22:00 every 15 minutes.

environment:
  - WATCHTOWER_SCHEDULE=0 */15 9-22 * * 1-5

Manually trigger deploy

In this setup Watchtower exposes a HTTP API on port 8080. To trigger a deploy you can use the following command:

curl -H "Authorization: Bearer 12345678" https://host.company.nl/update/v1

If you want to expose this over the internet with Caddy you can use the following configuration:

api.you.nl {
  tls /config/cert.nl.pem /config/cert.nl.key
  handle /v1/update {
     reverse_proxy http://deployer:8080
  }
  handle {
    reverse_proxy http://app:80
  }
}

The deployer container should be on the same network as the caddy and app containers. And /v1/update is the endpoint that triggers the deploy. And all other requests are proxied to the app container.

Compose file with 1 watched and 1 not

version: '3.3'

services:
  caddy:
    image: caddy:latest
    container_name: caddy
    restart: unless-stopped
    ports:
      - 0.0.0.0:443:443
    volumes:
      - ./Caddyfile:/etc/caddy/Caddyfile
      - ./caddy_data:/data
      - ./caddy_config:/config
    labels:
      - "com.centurylinklabs.watchtower.enable=false"
    networks:
      - internal

  app:
    image: company/app:latest
    container_name: app
    restart: unless-stopped
    labels:
      - "com.centurylinklabs.watchtower.enable=true"
    env_file:
      - ./.env
    networks:
      - internal

  deployer:
    image: containrrr/watchtower
    container_name: deployer
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
      - /root/.docker/config.json:/config.json
    command: --debug --http-api-update
    environment:
      - WATCHTOWER_HTTP_API_TOKEN=12345678
    labels:
      - "com.centurylinklabs.watchtower.enable=false"
    networks:
      - internal

networks:
  internal: