warp/Docker-AIO/docker-compose.pocketbase.seaweedfs.yml

# Warp all-in-one on PocketBase with SeaweedFS: the homeserver, the admin
# panel, the web client and SeaweedFS (one `weed server -s3` process) in one
# container built from this checkout (Dockerfile.PocketBase.SeaweedFS).
#
#   cd Docker-AIO
#   cp .env.pocketbase.seaweedfs.example .env      # then edit it
#   docker compose -f docker-compose.pocketbase.seaweedfs.yml up -d --build
#
# PocketBase runs in the container, its database in /data/pb_data
# (warp-data), admin UI on loopback at http://localhost:8070/_/; media goes to the bucket
# WARP_PB_S3_BUCKET in SeaweedFS (seaweed-data), whose gateway has exactly
# one identity: the homeserver's. 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. The S3 gateway (8333) is not published: the
# homeserver reaches it over the compose network.
#
# This and docker-compose.pocketbase.seaweedfs.split.yml share their project
# and volumes: SeaweedFS's data has the same layout either way, so switching
# between them needs no migration.
#
# Create the first administrator once the server is up:
#
#   docker compose -f docker-compose.pocketbase.seaweedfs.yml exec warp warp create-account --username admin --admin
#
# or set WARP_ADMIN_USERNAME and WARP_ADMIN_PASSWORD in .env, and the first
# start creates it.

name: warp-aio-pocketbase-seaweedfs

services:
  warp:
    build:
      context: ..
      dockerfile: Docker-AIO/Dockerfile.PocketBase.SeaweedFS
      args:
        # Passed only when set, so the Dockerfile's pin stays otherwise.
        - SEAWEED_VERSION
    image: warp-aio-pocketbase-seaweedfs:latest
    restart: unless-stopped
    env_file: .env
    environment:
      # The gateway is in the container at a fixed address; these override
      # whatever .env says about S3.
      WARP_PB_S3_ENABLED: "true"
      WARP_PB_S3_ENDPOINT: http://127.0.0.1:8333
      WARP_PB_S3_BUCKET: ${WARP_PB_S3_BUCKET:-warp}
      # SeaweedFS ignores the region; the client wants one.
      WARP_PB_S3_REGION: ${WARP_PB_S3_REGION:-us-east-1}
      WARP_PB_S3_FORCE_PATH_STYLE: "true"
      # The gateway's only identity, and what the homeserver signs with.
      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}
    volumes:
      - ${WARP_DATA_VOLUME:-warp-data}:/data
      - ${SEAWEED_DATA_VOLUME:-seaweed-data}:/seaweed/data
    ports:
      - "${WARP_PORT:-8008}:8008"
      - "${WARP_ADMIN_PORT:-8009}:8009"
      - "${WARP_WEB_PORT:-8080}:8080"
      - "${WARP_PB_BIND:-127.0.0.1}:${WARP_PB_PORT:-8070}:8070"

  # Calls: the LiveKit SFU and the LiveKit JWT service (docs/calls.md),
  # started only with the calls profile, COMPOSE_PROFILES=calls in .env.
  # Warp hands browsers the JWT service's URL from
  # WARP_RTC_LIVEKIT_SERVICE_URL, and the JWT service hands them
  # LIVEKIT_PUBLIC_URL; put both behind a TLS proxy. The media does not go
  # through the proxy: forward LIVEKIT_RTC_TCP_PORT and LIVEKIT_RTC_UDP_PORT
  # from the internet to this host.
  livekit:
    image: ${LIVEKIT_IMAGE:-livekit/livekit-server:v1.13.7}
    profiles: [calls]
    restart: unless-stopped
    environment:
      # node_ip is the address LiveKit tells browsers to send media to:
      # LIVEKIT_NODE_IP, or else the public address it finds over STUN.
      LIVEKIT_CONFIG: |
        port: 7880
        bind_addresses: [""]
        rtc:
          tcp_port: ${LIVEKIT_RTC_TCP_PORT:-7881}
          udp_port: ${LIVEKIT_RTC_UDP_PORT:-7882}
          use_external_ip: ${LIVEKIT_USE_EXTERNAL_IP:-true}
          node_ip: "${LIVEKIT_NODE_IP:-}"
        room:
          auto_create: false
        keys:
          "${LIVEKIT_KEY:-warp}": "${LIVEKIT_SECRET:-}"
        logging:
          level: info
    ports:
      - "${LIVEKIT_PORT:-7880}:7880"
      - "${LIVEKIT_RTC_TCP_PORT:-7881}:${LIVEKIT_RTC_TCP_PORT:-7881}"
      - "${LIVEKIT_RTC_UDP_PORT:-7882}:${LIVEKIT_RTC_UDP_PORT:-7882}/udp"

  # Gives a signed-in user a LiveKit token, after checking their OpenID
  # token with the homeserver at https://<server name>: through
  # /.well-known/matrix/server, which Warp serves only with federation on,
  # so with it off the well-known service below serves that file.
  livekit-jwt:
    image: ${LIVEKIT_JWT_IMAGE:-ghcr.io/element-hq/lk-jwt-service:0.8.0}
    profiles: [calls]
    restart: unless-stopped
    depends_on:
      - livekit
    environment:
      LIVEKIT_JWT_BIND: ":8080"
      # The URL handed to browsers, and the one the service creates rooms
      # through.
      LIVEKIT_URL: ${LIVEKIT_PUBLIC_URL:-}
      LIVEKIT_KEY: ${LIVEKIT_KEY:-warp}
      LIVEKIT_SECRET: ${LIVEKIT_SECRET:-}
      # Users of this server may create call rooms on the SFU.
      LIVEKIT_FULL_ACCESS_HOMESERVERS: ${WARP_SERVER_NAME:-localhost}
    ports:
      - "${LIVEKIT_JWT_PORT:-8071}:8080"

  # Serves /.well-known/matrix/server, which Warp serves only with
  # federation on, for the JWT service to find the homeserver by: route
  # that one path to it on the proxy, ahead of /.well-known/matrix/*. It
  # answers WARP_WELL_KNOWN_SERVER_ADDRESS, or <server name>:443, and 404
  # to everything else.
  well-known:
    image: ${WARP_WELL_KNOWN_IMAGE:-caddy:2.10.2-alpine}
    profiles: [calls]
    restart: unless-stopped
    configs:
      - source: well-known
        target: /etc/caddy/Caddyfile
    ports:
      - "${WARP_WELL_KNOWN_PORT:-8072}:8080"

volumes:
  warp-data:
  seaweed-data:

configs:
  # The well-known service's Caddyfile.
  well-known:
    content: |
      {
      	admin off
      	auto_https off
      }
      :8080 {
      	handle /.well-known/matrix/server {
      		header Content-Type application/json
      		header Access-Control-Allow-Origin *
      		respond `{"m.server":"${WARP_WELL_KNOWN_SERVER_ADDRESS:-${WARP_SERVER_NAME:-localhost}:443}"}` 200
      	}
      	respond 404
      }