tajniak81andClaude Opus 5
fe1e314df9
`weed server -s3` was never one thing. Master, volume, filer and the S3 gateway ran as four goroutines under one process, on one volume, sharing one fate. Splitting them into four containers changes nothing a client can see — the same bucket answers on the same port — but it makes three things possible that were not: the SeaweedFS admin UI, which wants a cluster to look at; a restart or an upgrade of one role without the others; and, eventually, a second volume server somewhere else. A fifth container carries the panel itself. The single-process files stay exactly as they were. These are `.split.` twins beside them, four in all, one per folder per shape, each with the .env example of the same name that both READMEs already promise. Identities are the part that could not simply be copied across. SeaweedFS picks its credentials from one source, in order: an -s3.config file, the filer's IAM store, then AWS_ACCESS_KEY_ID and its secret — and a higher source replaces a lower one rather than adding to it. The existing files use the env pair, which is fine precisely because nothing else writes identities there. Hand somebody a panel that can, and the first user they create lands in the filer's store, the store outranks the environment, and PocketBase's key stops existing — with the first failed upload as the notification. So the gateway here is started with no config file and no AWS_* at all, and the init container seeds PocketBase's identity into the filer's store instead: the same store the panel writes. One source of truth, PocketBase's key sitting in Object Store → Users beside every other, keys minted there picked up without a restart, and a rotated PB_S3_SECRET re-applied in place on the next boot rather than added as a second identity. That seeding is now allowed to fail. The bucket-create it grew out of was best-effort — `|| true`, on the reasoning that the API Server's own S3 check would report a gateway that was genuinely unreachable. That reasoning does not survive the change: a gateway whose IAM store is empty does not refuse anyone, it serves everyone, and the bucket would be wide open rather than unreachable. So the step ends by grepping the configuration back for the access key, the gateway waits on it completing successfully, and a seed that did not land stops the stack instead of opening it. The prod files publish the gateway and the panel, both on loopback, and nothing else. Port 8080 on the volume server hands out file content by file id with no authentication of any kind — the S3 credentials have no bearing on it — so publishing it would publish every attachment in the stack, and the panel shows what that port and the master's would. The panel's own password is required rather than defaulted, because weed serves it with authentication switched off entirely when it is empty, and a page that mints bucket credentials is the bucket. It is passed as WEED_ADMIN_PASSWORD rather than a flag so it stays off the process command line, and SEAWEED_ADMIN_BIND is the knob a remote host needs, named after PB_BIND and API_BIND for the same reason. Master, volume and filer share one /data mount rather than taking three of their own. That is precisely the layout `weed server -dir=/data` writes — the master's raft state, the volume's .dat and .idx, the filer's filerldb2, no two of them naming the same file — so a stack can move between the single-process file and its twin in either direction with nothing to migrate. A second volume server would need its own, and the files say so where somebody would go looking. The dev files map the volume server to 8081 on the host: 8080 there is already the API Server, and in the all-in-one it is the API Server inside the image. Unexercised: written on a machine without Docker, so none of the four has been brought up. Every flag, health path and env name was read out of the pinned 4.45 source rather than recalled — -mdir, -volumeSizeLimitMB, -defaultStoreDir, -max, admin's -master and -dataDir and WEED_ADMIN_*, the filer's and gateway's /healthz, the panel's unauthenticated /health — and the four files were parsed, interpolated against their examples, and checked for duplicate host ports. A `docker compose config` on the target host is still the first thing to run. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
167 lines
8.6 KiB
Bash
167 lines
8.6 KiB
Bash
# DriverVault — production stack config, SeaweedFS split into its four roles.
|
|
# 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/drivervault-pocketbase:latest
|
|
API_IMAGE=10.2.1.10:5500/admin/drivervault-api-server:latest
|
|
WEB_IMAGE=10.2.1.10:5500/admin/drivervault-web-app:latest
|
|
|
|
# --- PocketBase superuser ----------------------------------------------------
|
|
# Created/updated on the PocketBase container's first boot. The API Server uses
|
|
# these same credentials to manage the database. REQUIRED.
|
|
PB_ADMIN_EMAIL=admin@example.com
|
|
PB_ADMIN_PASSWORD=change-me-long-password
|
|
|
|
# --- DriverVault super-admin (app login) -------------------------------------
|
|
# The first application user, created by the API Server on boot with role
|
|
# "superadmin" if no user with this email exists yet. Leave blank to skip and
|
|
# create the first user by hand. This is the account you log in to the web app
|
|
# with — distinct from the PocketBase superuser above.
|
|
DRIVERVAULT_SUPERADMIN_EMAIL=owner@example.com
|
|
DRIVERVAULT_SUPERADMIN_PASSWORD=change-me-long-password
|
|
DRIVERVAULT_SUPERADMIN_NAME=Administrator
|
|
|
|
# Schema creation/reconcile on boot. Leave this true: a release can add
|
|
# collections or fields the server needs, and a stack that skips the bootstrap
|
|
# never gets them. (The API Server creates app_settings, which holds the plugin
|
|
# settings, on demand — but only that one.) Set false only for a database you
|
|
# know already matches the release.
|
|
PB_BOOTSTRAP=true
|
|
|
|
# --- API Server --------------------------------------------------------------
|
|
# Allowed CORS origin(s) for the web app (match your public URL / WEB_PORT).
|
|
CORS_ALLOW_ORIGINS=http://localhost:8090
|
|
AUTH_USERS_COLLECTION=users
|
|
|
|
# --- EV charging control (Anker Solix, OCPP) ---------------------------------
|
|
# Only relevant when a charger is set to own/proxy control mode. The charger
|
|
# dials in to /ocpp/{serial} on the API Server port, carrying its control token
|
|
# in an OCPP Basic-auth header — which a plaintext ws:// would expose, so
|
|
# non-TLS connections are rejected by default. Keep the default and terminate
|
|
# TLS in a reverse proxy in front of this stack, setting OCPP_PUBLIC_URL to the
|
|
# public wss:// base the charger should be pointed at (deriving it from request
|
|
# headers is unreliable behind a proxy). Turning the check off is for trusted
|
|
# networks only.
|
|
OCPP_REQUIRE_TLS=true
|
|
OCPP_PUBLIC_URL=
|
|
|
|
# Diagnostic only. Set to 1 to log every frame the charger publishes over Anker's
|
|
# cloud broker — the ones DriverVault decodes and the ones it cannot, with their
|
|
# bytes. It is how an unnamed frame gets named: hold a control read open, do the
|
|
# thing in the Anker app, then read the frames back out of the container log.
|
|
# Leave blank on a normal stack; a triggered charger writes a line every few
|
|
# seconds.
|
|
ANKER_MQTT_FRAME_LOG=
|
|
|
|
# The charger can dial either door: the API Server port directly, or the Web
|
|
# App port, whose BFF now proxies /ocpp/ through to it. The endpoint the panel
|
|
# shows is the API Server port only when OCPP_PUBLIC_URL says so — left blank it
|
|
# is whichever host the panel itself was reached on, which is the Web App.
|
|
# TRUST_FORWARDED_PROTO lets the BFF pass an inbound X-Forwarded-Proto to the
|
|
# API Server: needed when TLS ends at a proxy in front of the stack and
|
|
# OCPP_REQUIRE_TLS stays on, and unsafe otherwise, since the header is then
|
|
# whatever the client said it was.
|
|
TRUST_FORWARDED_PROTO=false
|
|
|
|
# --- 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 -----------------------------------------------------------------
|
|
# One Docker-managed named volume by default. To store it on a host path
|
|
# instead, set an absolute path, e.g. PB_DATA=/srv/drivervault/pb_data.
|
|
# PB_DATA — the PocketBase database and its backups. The API Server keeps no
|
|
# state on disk, so everything it owns (plugin settings included) is backed up
|
|
# by backing up this one path — together with SEAWEED_DATA below.
|
|
PB_DATA=pb_data
|
|
|
|
# --- File storage: SeaweedFS -------------------------------------------------
|
|
# PocketBase keeps its record files — document scans, service and refill
|
|
# receipts, workshop invoices, part photos — 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 "drivervault" *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=drivervault
|
|
# 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 attachments 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 port is published on loopback only — the stack reaches the gateway over
|
|
# the compose network, and this is for tools like aws-cli. Set
|
|
# SEAWEED_S3_BIND=0.0.0.0 to expose it to other hosts, and mean it.
|
|
# SEAWEED_S3_BIND=127.0.0.1
|
|
# SEAWEED_S3_PORT=8333
|
|
#
|
|
# The 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 attachments made before the switch stop resolving. Read the file
|
|
# storage section of README.md first.
|