# The SQLInsight Pro website behind Caddy, which gets and renews the TLS certificate itself.
# DNS for COMMUNITY_HOST must point at this server, and ports 80 and 443 must be free (Discourse runs on its own server).
#
#   COMMUNITY_HOST=sqlinsight.seosoft.dk docker compose up -d
services:
  community:
    build:
      context: ../..
      dockerfile: deploy/community/Dockerfile
    image: sqlinsight-community
    restart: unless-stopped
    environment:
      # The signed update feed: the hub's /updates/ (or a folder mounted into the container).
      SQLInsight__Community__Feed: ${COMMUNITY_FEED:-https://hub.sqlinsight.seosoft.dk/updates/}
      SQLInsight__Community__ForumUrl: ${COMMUNITY_FORUM:-https://forum.sqlinsight.seosoft.dk/}
      SQLInsight__Community__ContactEmail: ${COMMUNITY_CONTACT:?set COMMUNITY_CONTACT (the address for support enquiries)}
      # The public key releases are signed with, if it is not embedded in the build (the vendor tool's keygen prints it):
      # SQLInsight__Community__TrustedKeys__k20260929: "MFkw..."
    expose:
      - "8080"

  caddy:
    image: caddy:2-alpine
    restart: unless-stopped
    depends_on:
      - community
    environment:
      COMMUNITY_HOST: ${COMMUNITY_HOST:?set COMMUNITY_HOST}
    ports:
      - "80:80"
      - "443:443"
    volumes:
      - ./Caddyfile:/etc/caddy/Caddyfile:ro
      - caddy_data:/data
      - caddy_config:/config

volumes:
  caddy_data:
  caddy_config: