Files
PilotVault/Docker-AIO/docker-compose.prod.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

54 lines
2.5 KiB
YAML

name: pilotvault-aio
# Production all-in-one — pulls the prebuilt image from the registry instead of
# building. One container runs PocketBase + API Server + Web App (Go BFF).
# Everything an operator needs to set lives in .env.
#
# 1. cp .env.prod.example .env (then edit it)
# 2. docker compose -f docker-compose.prod.yml pull
# 3. docker compose -f docker-compose.prod.yml up -d
#
# 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
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}"
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: