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

145 lines
6.8 KiB
YAML

name: pilotvault-aio
# Single all-in-one container, with SeaweedFS: PocketBase + API Server + Web App
# (Go BFF) in one image, plus an S3 object store beside it. Self-contained — one
# file, nothing to layer.
#
# cp .env.seaweedfs.example .env (then edit it)
# docker compose -f docker-compose.seaweedfs.yml up -d --build
#
# The build context is the project root so the Dockerfile can reach both "API
# Server/" and "Web App/".
#
# 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 a SeaweedFS 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.
#
# SeaweedFS runs as a second container beside the all-in-one, not as a fourth
# process inside it: keeping the object store in that image, on the volume the
# files are being moved off, would defeat the point and would mean rebuilding.
#
# Before turning this on for a stack that already has uploads: PocketBase does
# NOT copy existing files into the bucket. See README.md.
services:
seaweedfs:
image: "${SEAWEED_IMAGE:-chrislusf/seaweedfs:4.45}"
container_name: pilotvault-aio-seaweedfs
restart: unless-stopped
# One process, four roles: master, volume, filer and the S3 gateway. -dir is
# the only state it keeps.
command: server -dir=/data -s3 -master.volumeSizeLimitMB=1024
environment:
# SeaweedFS falls back to these when started without an -s3.config file,
# and configuring one identity is what takes the S3 gateway out of its
# default allow-anyone mode. The same credentials PocketBase authenticates
# with below — one pair to set, in .env.
AWS_ACCESS_KEY_ID: "${PB_S3_ACCESS_KEY:?set PB_S3_ACCESS_KEY in .env}"
AWS_SECRET_ACCESS_KEY: "${PB_S3_SECRET:?set PB_S3_SECRET in .env}"
volumes:
# From here on the documents live here, not on pb_data.
- seaweed_data:/data
# No published port: the stack reaches the gateway over the compose network.
healthcheck:
test: ["CMD-SHELL", "wget -qO- http://127.0.0.1:9333/cluster/status || exit 1"]
interval: 10s
timeout: 3s
retries: 12
start_period: 20s
seaweedfs-init:
image: "${SEAWEED_IMAGE:-chrislusf/seaweedfs:4.45}"
container_name: pilotvault-aio-seaweedfs-init
# Runs once and exits. PocketBase never issues a CreateBucket of its own and
# SeaweedFS will not conjure one on first upload, so something has to.
# Creating a bucket that already exists is a no-op, so every later boot
# passes straight through.
restart: "no"
depends_on:
seaweedfs:
condition: service_healthy
entrypoint: ["/bin/sh", "-c"]
# `|| true` so a restart is never blocked by the shell's exit status: this
# step is best-effort, and a gateway that is genuinely unreachable is
# reported by the API Server's own S3 check at boot, with the reason.
command:
- 'echo "s3.bucket.create -name ${PB_S3_BUCKET:-pilotvault}" | weed shell -master=seaweedfs:9333 || true'
pilotvault:
build:
# Project root (one level up from this compose file).
context: ..
dockerfile: Docker-AIO/Dockerfile
args:
# Bare name = pass through only when set in the environment, so an unset
# PB_VERSION leaves the Dockerfile pin in place instead of overriding it
# with an empty string (which would resolve "latest" at build time).
- PB_VERSION
image: pilotvault-aio
container_name: pilotvault-aio
restart: unless-stopped
depends_on:
# PocketBase — inside this container — is the process that reads and
# writes the objects, so the gateway has to be serving first, and the
# bucket has to exist before the API Server points PocketBase at it.
seaweedfs:
condition: service_healthy
seaweedfs-init:
condition: service_completed_successfully
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.
PB_S3_ENABLED: "true"
PB_S3_BUCKET: "${PB_S3_BUCKET:-pilotvault}"
# The service name: a server-to-server call inside the compose network.
PB_S3_ENDPOINT: "http://seaweedfs:8333"
# SeaweedFS ignores the region; PocketBase insists on having one.
PB_S3_REGION: "${PB_S3_REGION:-us-east-1}"
PB_S3_ACCESS_KEY: "${PB_S3_ACCESS_KEY}"
PB_S3_SECRET: "${PB_S3_SECRET}"
# Path style, because a self-hosted gateway has no per-bucket DNS.
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). Back up
# PB_DATA and SEAWEED_DATA together — from here on the documents live in
# the second, not the first.
- "${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:
seaweed_data: