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>
92 lines
4.5 KiB
Bash
92 lines
4.5 KiB
Bash
# Copy to .env and fill in. Used by docker-compose.seaweedfs.split.yml.
|
|
|
|
# --- PocketBase superuser (also used by the API Server to authenticate) ------
|
|
# Created/updated on the PocketBase container's first boot. REQUIRED.
|
|
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 — no separate env var needed.
|
|
|
|
# --- 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) --------------------------
|
|
PB_PORT=8070
|
|
API_PORT=8080
|
|
WEB_PORT=8090
|
|
|
|
# --- 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.
|
|
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
|
|
# The SeaweedFS image, pinned so a rebuild months from now brings up the same
|
|
# one. All five SeaweedFS containers run it.
|
|
# SEAWEED_IMAGE=chrislusf/seaweedfs:4.45
|
|
|
|
# --- SeaweedFS admin UI ------------------------------------------------------
|
|
# http://localhost:23646 — cluster topology, volumes, buckets, 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=
|
|
# SEAWEED_ADMIN_PORT=23646
|
|
|
|
# --- SeaweedFS host ports (optional; defaults shown) -------------------------
|
|
# Published for aws-cli, `weed shell` and poking around while developing. The
|
|
# stack itself reaches every one of these over the compose network, and the S3
|
|
# gateway too, which is not published so a second stack cannot clash on it. Note
|
|
# SEAWEED_VOLUME_PORT: the volume server serves file content by id with NO
|
|
# authentication, so do not carry this mapping over to a shared machine. It
|
|
# lands on 8081 because API_PORT already has 8080.
|
|
# SEAWEED_MASTER_PORT=9333
|
|
# SEAWEED_VOLUME_PORT=8081
|
|
# SEAWEED_FILER_PORT=8888
|
|
|
|
# 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.
|