Files
PilotVault/Docker-AIO/docker-compose.prod.s3.yml
T
tajniak81andClaude Opus 5.5 3962530841 Docker-AIO: S3 and SeaweedFS variants, matching DriverVault
Docker-AIO gets the same deployment shapes as DriverVault: plain,
SeaweedFS, SeaweedFS split into its roles, and an external S3 endpoint,
each as a build-from-source and a prod compose file with an .env example
of the same name, plus a README. The from-source SeaweedFS files run the
store as side containers; the prod ones build Dockerfile.seaweedfs or
Dockerfile.seaweedfs.split, which bake `weed server -s3` or its five
separate roles into the image under supervisord.

The image is rebuilt around PilotVault's real layout. The old Dockerfile
copied "Web App/ui" and "Web App/main.go", which no longer exist, and
pinned PocketBase 0.22.21, which cannot run the migrations; it now builds
"Web App/web" + "Web App/server" and pins 0.39.11. Unlike DriverVault's
nginx front, the Go BFF keeps serving the UI on 8090. Every process runs
as an unprivileged user, plugins.json gets an /app/data volume, the
container is healthy only when every process answers, and no default
superuser credentials are baked in.

Verified on Docker from an empty database: plain, both SeaweedFS
from-source and both baked prod variants come up healthy, document
uploads land in the bucket and download back. The external-S3 files are
checked with `docker compose config` only.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-17 18:08:53 +01:00

88 lines
4.4 KiB
YAML

name: pilotvault-aio
# Production all-in-one, with external S3 — pulls the prebuilt image from the
# registry instead of building. Self-contained: one file, no overlays.
# Everything an operator needs to set lives in .env.
#
# 1. cp .env.prod.s3.example .env (then edit it — PB_S3_* especially)
# 2. docker compose -f docker-compose.prod.s3.yml pull
# 3. docker compose -f docker-compose.prod.s3.yml up -d
#
# This is docker-compose.prod.yml pointed at an S3 endpoint that already exists
# somewhere else — its own host, another compose project, or any S3-compatible
# service. 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. 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 container, use
# docker-compose.prod.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.
#
# On first boot PocketBase upserts the superuser from POCKETBASE_ADMIN_*, and
# runs the bundled migrations (every collection, the baseline org and the
# superadmin@pilotvault.local login). Both steps are idempotent.
services:
pilotvault:
image: "${AIO_IMAGE:-10.2.1.10:5500/admin/pilotvault-aio:latest}"
container_name: pilotvault-aio
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:
# Superuser (also used by the API Server to authenticate to PocketBase).
POCKETBASE_ADMIN_EMAIL: "${POCKETBASE_ADMIN_EMAIL:?set POCKETBASE_ADMIN_EMAIL in .env}"
POCKETBASE_ADMIN_PASSWORD: "${POCKETBASE_ADMIN_PASSWORD:?set POCKETBASE_ADMIN_PASSWORD in .env}"
# Match CORS to the web origin (only used if a browser calls the API
# directly).
CORS_ALLOW_ORIGINS: "${CORS_ALLOW_ORIGINS:-http://localhost:8090}"
# Probed by the panel status page. The Web App BFF listens on 8090 inside
# this container too. Override WEBAPP_URL in .env to make a change from
# the panel permanent; the panel alone only holds it for the container's
# life.
WEBAPP_URL: "${WEBAPP_URL:-http://127.0.0.1:8090}"
# --- File storage --------------------------------------------------
# supervisord passes these through to the API Server, which writes them
# into PocketBase's settings on every boot, 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}"
ports:
- "${WEB_PORT:-8090}:8090" # Web App (Go BFF)
- "${PB_PORT:-8070}:8070" # PocketBase admin UI / API
- "${API_PORT:-8080}:8080" # API Server + panel (root /)
volumes:
# Named volumes by default; set any of them to a host path in .env for a
# bind mount. PB_DATA: the database and PocketBase's backups. API_DATA:
# the API Server's plugins.json (plugin enable-state + config).
- "${PB_DATA:-pb_data}:/pb/pb_data"
- "${API_DATA:-api_data}:/app/data"
healthcheck:
# All three processes must answer. Declared here as well as in the image
# so the check is visible, and works against an older pulled image.
test: ["CMD-SHELL", "wget -qO- http://127.0.0.1:8070/api/health >/dev/null && wget -qO- http://127.0.0.1:8080/healthz >/dev/null && wget -qO- http://127.0.0.1:8090/ >/dev/null || exit 1"]
interval: 30s
timeout: 5s
retries: 3
start_period: 60s
volumes:
pb_data:
api_data: