Docker/ gets the same deployment shapes as DriverVault: plain, SeaweedFS in the stack, SeaweedFS split into its roles, and an external S3 endpoint, each as a build-from-source and a registry compose file with an .env example of the same name, plus a README. The API Server now reads PB_S3_* on boot and points PocketBase's file storage at the bucket (only when the settings differ), then asks PocketBase to test it. It never turns S3 off. Plugin state gets an api_data volume, since the image could not write plugins.json. The PocketBase image pinned v0.22.21, which cannot run the v0.23+ migrations or `superuser upsert`; it now pins v0.39.11. Starting from an empty database also exposed two migration bugs: the seed tried to create a passwordless account, and the documents collection saved its self-relation with a blank target. Both are fixed; databases that already ran them are unaffected. Verified on Docker: the SeaweedFS and split stacks come up healthy from an empty database, uploads land in the bucket, and a restart is a no-op. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
121 lines
6.0 KiB
Bash
121 lines
6.0 KiB
Bash
# PilotVault — production stack config.
|
|
# Copy to .env and fill in, then:
|
|
# docker compose -f docker-compose.prod.seaweedfs.split.yml pull
|
|
# docker compose -f docker-compose.prod.seaweedfs.split.yml up -d
|
|
|
|
# --- Registry images --------------------------------------------------------
|
|
# Defaults point at the internal registry; override to pin a tag or use a mirror.
|
|
PB_IMAGE=10.2.1.10:5500/admin/pilotvault-pocketbase:latest
|
|
API_IMAGE=10.2.1.10:5500/admin/pilotvault-api-server:latest
|
|
WEB_IMAGE=10.2.1.10:5500/admin/pilotvault-web-app:latest
|
|
|
|
# --- PocketBase superuser (required) ----------------------------------------
|
|
# Created/updated on the PocketBase container's first boot. The API Server uses
|
|
# these same credentials to manage the database.
|
|
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 your public URL / WEB_PORT).
|
|
CORS_ALLOW_ORIGINS=http://localhost:8090
|
|
|
|
# --- Ports -------------------------------------------------------------------
|
|
# WEB_PORT is the public front door (bound on all interfaces).
|
|
WEB_PORT=8090
|
|
# PocketBase admin UI and the API panel are bound to localhost only by default.
|
|
# Set PB_BIND / API_BIND to 0.0.0.0 to expose them on the network — which is
|
|
# what a stack running on a remote host needs, behind a reverse proxy.
|
|
PB_PORT=8070
|
|
PB_BIND=127.0.0.1
|
|
API_PORT=8080
|
|
API_BIND=127.0.0.1
|
|
|
|
# --- 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 where the API Server looks for the database. Defaults to
|
|
# the bundled pocketbase service; set it to reach one
|
|
# outside this stack.
|
|
# WEBAPP_URL the Web App address the panel status page probes. It is
|
|
# a container-to-container call, so it must be reachable
|
|
# from the API Server, not from your browser.
|
|
# CORS_ALLOW_ORIGINS browser origins allowed to call the API Server directly.
|
|
# POCKETBASE_URL=http://pocketbase:8070
|
|
# WEBAPP_URL=http://web-app: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). A
|
|
# host path must be writable by uid 10001, the image's runtime user.
|
|
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: seaweedfs-init 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 stack 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 seaweedfs-init container.
|
|
PB_S3_BUCKET=pilotvault
|
|
# SeaweedFS ignores the region; PocketBase insists on having one.
|
|
PB_S3_REGION=us-east-1
|
|
|
|
# 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.
|
|
#
|
|
# The master, volume and filer containers all mount it at /data, which is the
|
|
# layout `weed server -dir=/data` 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 SeaweedFS image, pinned so a redeploy months from now brings up the same
|
|
# one. All five SeaweedFS containers run it.
|
|
# SEAWEED_IMAGE=chrislusf/seaweedfs:4.45
|
|
# The S3 gateway, master, volume and filer 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, so it stays on the compose network.
|
|
# Reach the others with `docker compose exec`.
|
|
|
|
# --- 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.
|
|
SEAWEED_ADMIN_USER=admin
|
|
SEAWEED_ADMIN_PASSWORD=
|
|
# Optional view-only login.
|
|
SEAWEED_ADMIN_READONLY_USER=
|
|
SEAWEED_ADMIN_READONLY_PASSWORD=
|
|
# Bound to localhost by default, like PB_BIND and API_BIND. On a remote host
|
|
# that means unreachable — set 0.0.0.0 and put it behind the same reverse proxy
|
|
# as the other panels.
|
|
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.
|