# Warp on PocketBase with media in an S3 bucket elsewhere: the homeserver,
# the admin panel and the web client, each in its own container, pulled
# from a registry.
#
#   cd Docker
#   cp .env.pocketbase.s3.prod.example .env      # then edit it
#   docker compose -f docker-compose.pocketbase.s3.prod.yml up -d
#
# The database is PocketBase's, in pb-data; media goes to the bucket
# WARP_PB_S3_BUCKET (default warp) on WARP_PB_S3_ENDPOINT, which must already
# exist: nothing here runs a gateway or creates the bucket. For a gateway on
# this Docker host, use http://host.docker.internal:8333; the host entry below
# makes that name resolve. For a SeaweedFS that comes up with the stack, see
# docker-compose.pocketbase.seaweedfs.yml. Media stored before S3 was on is
# not moved into the bucket.
#
# Homeserver http://localhost:8008, admin panel http://localhost:8009, web
# client http://localhost:8080.
#
# Create the first administrator once the server is up:
#
#   docker compose -f docker-compose.pocketbase.s3.prod.yml exec warp warp create-account --username admin --admin
#
# Nothing is built here: the homeserver, admin panel and web client images
# come from WARP_REGISTRY (default 10.2.1.10:5500/admin) at tag
# WARP_VERSION (default latest). Pin WARP_VERSION to a release in
# production, and update with
#
#   docker compose -f docker-compose.pocketbase.s3.prod.yml pull && docker compose -f docker-compose.pocketbase.s3.prod.yml up -d

name: warp-pocketbase-s3

services:
  # PocketBase, the homeserver's database: Warp's collections, and media in
  # PocketBase's storage, are in the pb-data volume. The image creates the
  # superuser from .env on its first start, and never changes it after: a
  # new password goes in through the admin UI, then into .env. The admin UI
  # is http://localhost:8070/_/ on loopback; WARP_PB_BIND=0.0.0.0 exposes
  # it, behind a reverse proxy only.
  pocketbase:
    image: ${WARP_PB_IMAGE:-tajniak81/pocketbase-docker-root:latest}
    pull_policy: always
    restart: unless-stopped
    extra_hosts:
      # Lets WARP_PB_S3_ENDPOINT name the Docker host as host.docker.internal:
      # PocketBase is what talks to the bucket.
      - "host.docker.internal:host-gateway"
    environment:
      PB_PORT: "8070"
      PB_ADMIN_EMAIL: ${WARP_PB_SUPERUSER_EMAIL:?set WARP_PB_SUPERUSER_EMAIL in .env}
      PB_ADMIN_PASSWORD: ${WARP_PB_SUPERUSER_PASSWORD:?set WARP_PB_SUPERUSER_PASSWORD in .env}
    volumes:
      - ${WARP_PB_DATA_VOLUME:-pb-data}:/pb/pb_data
    ports:
      - "${WARP_PB_BIND:-127.0.0.1}:${WARP_PB_PORT:-8070}:8070"
    healthcheck:
      test: ["CMD-SHELL", "wget -qO- http://127.0.0.1:8070/api/health >/dev/null || exit 1"]
      interval: 5s
      timeout: 3s
      retries: 20
      start_period: 10s

  warp:
    image: ${WARP_REGISTRY:-10.2.1.10:5500/admin}/warp:${WARP_VERSION:-latest}
    pull_policy: always
    restart: unless-stopped
    depends_on:
      pocketbase:
        condition: service_healthy
    extra_hosts:
      # Lets WARP_PB_S3_ENDPOINT name the Docker host as host.docker.internal.
      - "host.docker.internal:host-gateway"
    # The homeserver does not check the endpoint at startup and would only
    # fail on the first upload, so wait up to 30 seconds for it to answer at
    # all (any HTTP status). The signing key is created on first start and
    # kept in the volume: losing it means other servers no longer recognise
    # this one.
    entrypoint: ["/bin/sh", "-c"]
    command:
      - >-
        i=0; until curl -s -o /dev/null --max-time 5 "$$WARP_PB_S3_ENDPOINT"; do
        i=$$((i + 1)); if [ "$$i" -ge 30 ]; then echo "S3 endpoint $$WARP_PB_S3_ENDPOINT does not answer" >&2; exit 1; fi;
        echo "waiting for S3 endpoint $$WARP_PB_S3_ENDPOINT" >&2; sleep 1; done;
        test -f /data/signing.key || warp generate-keys --output /data/signing.key; exec warp serve
    env_file: .env
    environment:
      WARP_DB_DRIVER: pocketbase
      WARP_DB_CONNECTION_STRING: http://pocketbase:8070
      WARP_PB_S3_ENABLED: "true"
      WARP_PB_S3_ENDPOINT: ${WARP_PB_S3_ENDPOINT:?set WARP_PB_S3_ENDPOINT in .env}
      WARP_PB_S3_BUCKET: ${WARP_PB_S3_BUCKET:-warp}
      # SeaweedFS and MinIO ignore the region; the client insists on one.
      WARP_PB_S3_REGION: ${WARP_PB_S3_REGION:-us-east-1}
      WARP_PB_S3_ACCESS_KEY: ${WARP_PB_S3_ACCESS_KEY:?set WARP_PB_S3_ACCESS_KEY in .env}
      WARP_PB_S3_SECRET: ${WARP_PB_S3_SECRET:?set WARP_PB_S3_SECRET in .env}
      # true for SeaweedFS and MinIO, false for AWS S3 proper.
      WARP_PB_S3_FORCE_PATH_STYLE: ${WARP_PB_S3_FORCE_PATH_STYLE:-true}
    volumes:
      - ${WARP_DATA_VOLUME:-warp-data}:/data
    ports:
      - "${WARP_PORT:-8008}:8008"

  admin:
    image: ${WARP_REGISTRY:-10.2.1.10:5500/admin}/warp-admin:${WARP_VERSION:-latest}
    pull_policy: always
    restart: unless-stopped
    depends_on:
      - warp
    env_file: .env
    environment:
      WARP_ADMIN_HOMESERVER: http://warp:8008
    ports:
      - "${WARP_ADMIN_PORT:-8009}:8009"

  web:
    image: ${WARP_REGISTRY:-10.2.1.10:5500/admin}/warp-web:${WARP_VERSION:-latest}
    pull_policy: always
    restart: unless-stopped
    depends_on:
      - warp
    env_file: .env
    environment:
      WARP_WEB_HOMESERVER: http://warp:8008
    ports:
      - "${WARP_WEB_PORT:-8080}:8080"

volumes:
  # The homeserver's signing key.
  warp-data:
  # PocketBase's pb_data: the database, and media unless it is in S3.
  pb-data: