name: pilotvault # Full PilotVault stack, with external S3: PocketBase (database) + API Server + # Web App, built from source, storing files in an S3 endpoint that already # exists somewhere else. Self-contained — one file, nothing to layer. # # cp .env.s3.example .env (then edit it — PB_S3_* especially) # docker compose -f docker-compose.s3.yml up -d --build # # Traffic flow (browser): Web App BFF --/api--> API Server --> PocketBase. # # This is docker-compose.yml plus storage: PocketBase keeps its record files — # the document store's scans of pilot certificates, aircraft registrations, # insurance and authorisations — in that bucket instead of on the pb_data volume # next to the database. The database and PocketBase's own backups stay on # pb_data. Clients cannot tell the difference: a document has always been # downloaded through the API Server (GET /api/documents/{id}/file), never from a # storage URL. # # The bucket must already exist, and nothing here runs the gateway. For a # SeaweedFS that comes up with the stack, use docker-compose.seaweedfs.yml. # # Before turning this on for a stack that already has uploads: PocketBase does # NOT copy existing files into the bucket. See README.md. services: pocketbase: build: # Repo root — the Dockerfile bundles the migrations from "API Server/". context: .. dockerfile: Docker/pocketbase/Dockerfile image: pilotvault-pocketbase container_name: pilotvault-pocketbase restart: unless-stopped extra_hosts: # Lets PB_S3_ENDPOINT name the Docker host as host.docker.internal. # Harmless when the endpoint is somewhere else entirely. - "host.docker.internal:host-gateway" environment: # The superuser is created/updated on boot (the API Server authenticates # with it). This is the only place the first superuser can be created — the # REST API cannot bootstrap it. On the same boot PocketBase runs the bundled # migrations: every collection, plus the baseline org and the # superadmin@pilotvault.local app login. POCKETBASE_ADMIN_EMAIL: "${POCKETBASE_ADMIN_EMAIL:?set POCKETBASE_ADMIN_EMAIL in .env}" POCKETBASE_ADMIN_PASSWORD: "${POCKETBASE_ADMIN_PASSWORD:?set POCKETBASE_ADMIN_PASSWORD in .env}" volumes: # Named volume by default; set PB_DATA to a host path in .env for a bind mount. - "${PB_DATA:-pb_data}:/pb/pb_data" ports: # Admin UI / API exposed on the host for management (http://host:8070/_/). - "${PB_PORT:-8070}:8070" healthcheck: test: ["CMD-SHELL", "wget -qO- http://127.0.0.1:8070/api/health || exit 1"] interval: 10s timeout: 3s retries: 12 start_period: 10s api-server: build: context: "../API Server" image: pilotvault-api-server container_name: pilotvault-api-server restart: unless-stopped extra_hosts: # Lets PB_S3_ENDPOINT name the Docker host as host.docker.internal. # Harmless when the endpoint is somewhere else entirely. - "host.docker.internal:host-gateway" depends_on: pocketbase: condition: service_healthy environment: API_ADDR: ":8080" # Reach PocketBase by its service name on the internal network. Override # POCKETBASE_URL in .env to point the API Server at a database outside # this stack — that is also how you make a retarget done from the panel # permanent, since the panel's change lasts only for the container's life. POCKETBASE_URL: "${POCKETBASE_URL:-http://pocketbase:8070}" POCKETBASE_ADMIN_EMAIL: "${POCKETBASE_ADMIN_EMAIL}" POCKETBASE_ADMIN_PASSWORD: "${POCKETBASE_ADMIN_PASSWORD}" # Probed by the panel status page. This is a server-to-server call inside # the compose network, so the default is the service name — plain # localhost:8090 would resolve to this container itself. WEBAPP_URL: "${WEBAPP_URL:-http://web-app:8090}" # Same-origin requests go through the Web App BFF, so CORS is only needed # if a browser ever calls the API Server directly. Default to the web origin. CORS_ALLOW_ORIGINS: "${CORS_ALLOW_ORIGINS:-http://localhost:8090}" # Plugin enable-state + config, on the api_data volume below. PLUGINS_FILE: "/app/data/plugins.json" # --- File storage -------------------------------------------------- # The PilotVault API Server reads these on every boot and writes them into # PocketBase's Files storage settings, idempotently. Only record files # move — the document store's blobs. The database and PocketBase's own # backups stay on pb_data. The bucket must already exist: nothing here # creates it. PB_S3_ENABLED: "true" PB_S3_BUCKET: "${PB_S3_BUCKET:-pilotvault}" PB_S3_ENDPOINT: "${PB_S3_ENDPOINT:?set PB_S3_ENDPOINT in .env}" PB_S3_REGION: "${PB_S3_REGION:-us-east-1}" PB_S3_ACCESS_KEY: "${PB_S3_ACCESS_KEY:?set PB_S3_ACCESS_KEY in .env}" PB_S3_SECRET: "${PB_S3_SECRET:?set PB_S3_SECRET in .env}" # true for SeaweedFS and MinIO, false for AWS S3 proper. PB_S3_FORCE_PATH_STYLE: "${PB_S3_FORCE_PATH_STYLE:-true}" volumes: # The one thing the API Server keeps on disk: plugins.json. Named volume # by default; set API_DATA to a host path in .env for a bind mount (it # must be writable by uid 10001, the image's runtime user). - "${API_DATA:-api_data}:/app/data" ports: # Optional direct access to the API Server (and its panel at /); the Web # App reaches it over the internal network, not this host port. - "${API_PORT:-8080}:8080" healthcheck: # Declared here rather than relying only on the image's HEALTHCHECK, so the # depends_on gate below still works against an older pulled image. test: ["CMD-SHELL", "wget -qO- http://127.0.0.1:8080/healthz || exit 1"] interval: 10s timeout: 3s retries: 12 start_period: 20s web-app: build: context: "../Web App" image: pilotvault-web-app container_name: pilotvault-web-app restart: unless-stopped depends_on: # Wait for the API Server to be serving rather than merely started. api-server: condition: service_healthy environment: ADDR: ":8090" # The BFF reverse-proxies /api/* to the API Server over the internal network. API_BASE: "http://api-server:8080" ports: - "${WEB_PORT:-8090}:8090" healthcheck: # The BFF has no health route of its own; the SPA index answers 200. test: ["CMD-SHELL", "wget -qO- http://127.0.0.1:8090/ >/dev/null || exit 1"] interval: 10s timeout: 3s retries: 12 start_period: 10s volumes: pb_data: api_data: