Files
PilotVault/Docker-AIO/.env.prod.seaweedfs.split.example
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

115 lines
5.9 KiB
Bash

# PilotVault all-in-one — production config, SeaweedFS split into its roles and
# built into the same image (Dockerfile.seaweedfs.split). Copy to .env and fill in, then:
# docker compose -f docker-compose.prod.seaweedfs.split.yml build
# docker compose -f docker-compose.prod.seaweedfs.split.yml up -d
# The build needs the repo checkout; to deploy elsewhere, `push` after building
# and `pull` on the deploy host.
# --- Image -------------------------------------------------------------------
# The tag the build produces and `push`/`pull` use. Its own name, not
# pilotvault-aio: this image carries SeaweedFS and expects more volumes.
AIO_IMAGE=10.2.1.10:5500/admin/pilotvault-aio-seaweedfs-split:latest
# Build args, both pinned in the Dockerfile. Set to override at build time.
# PB_VERSION=0.39.11
# SEAWEED_VERSION=4.45
# --- PocketBase superuser (required) ----------------------------------------
# Created/updated on every boot; the API Server authenticates with the same
# credentials. No safe defaults.
POCKETBASE_ADMIN_EMAIL=admin@dji.local
POCKETBASE_ADMIN_PASSWORD=change-me-long-password
# The app super-admin login (superadmin@pilotvault.local) is created by the
# bundled PocketBase migrations on first boot — distinct from the superuser above.
# --- API Server -------------------------------------------------------------
# Allowed CORS origin(s) for the web app (match WEB_PORT / your public URL).
# Native apps are not subject to CORS.
CORS_ALLOW_ORIGINS=http://localhost:8090
# --- Host port mappings (optional; defaults shown) --------------------------
WEB_PORT=8090
PB_PORT=8070
API_PORT=8080
# --- Settings the API Server panel can also change ---------------------------
# The panel's Settings screens apply these immediately, but only for the life of
# the container — the values below are re-applied on every restart and win. Set
# them here to make a change permanent. (POCKETBASE_URL is fixed to this
# container's own PocketBase and is not meant to be repointed.)
# WEBAPP_URL the Web App address the panel status page probes; the
# BFF serves it on port 8090 inside this container.
# CORS_ALLOW_ORIGINS browser origins allowed to call the API Server directly.
# WEBAPP_URL=http://127.0.0.1:8090
# --- Storage ----------------------------------------------------------------
# Docker-managed named volumes by default. To store one on a host path instead,
# set an absolute path, e.g. PB_DATA=/srv/pilotvault/pb_data.
# PB_DATA — the PocketBase database and its backups.
# The documents themselves live in the bucket below.
# Back it up together with SEAWEED_DATA below.
PB_DATA=pb_data
# API_DATA — the API Server's plugins.json (plugin enable-state + config).
API_DATA=api_data
# --- File storage: SeaweedFS -------------------------------------------------
# PocketBase keeps its record files — the document store's scans of pilot
# certificates, aircraft registrations, insurance and authorisations — in the
# bucket below instead of on PB_DATA. The database and PocketBase's own backups
# stay where they are.
#
# The credentials do double duty: the S3 gateway's program writes them into the
# filer's IAM store as the identity named "pilotvault" *and* they are what
# PocketBase authenticates with. There are no safe defaults, and the container
# refuses to start without them. Change them here and restart to rotate: the
# seed updates the identity in place rather than adding a second one.
PB_S3_ACCESS_KEY=
PB_S3_SECRET=
# The bucket. Created on first boot by the S3 gateway's program.
PB_S3_BUCKET=pilotvault
# The endpoint, region and path style are fixed by the image — the gateway is
# inside the container at a loopback address that cannot change.
# SEAWEED_DATA — where SeaweedFS keeps the files. A Docker-managed named volume
# by default; set an absolute host path for a bind mount, the same way PB_DATA
# works above. Back it up alongside PB_DATA: from here on the documents live
# here, not in the database volume.
#
# Master, volume and filer share it (mounted at /seaweed/data), which is the
# layout `weed server -dir` writes — so this file and
# docker-compose.prod.seaweedfs.yml are interchangeable on the same volume, with
# nothing to migrate either way.
SEAWEED_DATA=seaweed_data
# The S3 gateway publishes no host port: PocketBase reaches it inside the
# container. The master, volume and filer listen on the container's loopback and
# publish no host port at all. The admin UI below shows what they would: the
# volume server in particular serves file content by id with no authentication.
# Reach them with `docker compose exec pilotvault wget -qO-
# http://127.0.0.1:9333/...` (volume 8081, filer 8888).
# --- SeaweedFS admin UI ------------------------------------------------------
# Cluster topology, volumes, buckets, maintenance tasks, and Object Store →
# Users, where further S3 identities are created and revoked. They land in the
# filer's IAM store, the same one seeded above, and the gateway picks them up
# without a restart.
#
# REQUIRED: weed disables authentication entirely when the password is empty,
# and this panel can mint credentials for the bucket — so the image refuses to
# start the panel at all without one, and the container stays unhealthy.
SEAWEED_ADMIN_USER=admin
SEAWEED_ADMIN_PASSWORD=
# Optional view-only login.
SEAWEED_ADMIN_READONLY_USER=
SEAWEED_ADMIN_READONLY_PASSWORD=
# Bound to localhost by default: storage plumbing, not one of the app's own
# panels. On a remote host that means unreachable — set 0.0.0.0 and put it
# behind a reverse proxy.
SEAWEED_ADMIN_BIND=127.0.0.1
SEAWEED_ADMIN_PORT=23646
# Its own small volume: session key and maintenance-task state, no object data.
SEAWEED_ADMIN_DATA=seaweed_admin
# Existing uploads are NOT migrated when this is switched on: PocketBase copies
# nothing, so documents uploaded before the switch stop resolving. Read the file
# storage section of README.md first.