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>
108 lines
5.4 KiB
Bash
108 lines
5.4 KiB
Bash
# Copy to .env and fill in. Used by the Docker-AIO
|
|
# docker-compose.seaweedfs.split.yml — the same stack as .env.seaweedfs.example,
|
|
# with SeaweedFS running as separate master / volume / filer / S3 containers
|
|
# plus the SeaweedFS admin UI.
|
|
|
|
# --- Required (no defaults) --------------------------------------------------
|
|
# PocketBase superuser, also used by the API Server to authenticate.
|
|
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.
|
|
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
|
|
|
|
# Allowed CORS origin(s) — match your web origin / WEB_PORT.
|
|
CORS_ALLOW_ORIGINS=http://localhost:8090
|
|
|
|
# --- 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. This image serves plain HTTP:
|
|
# either terminate TLS in front of it and set OCPP_PUBLIC_URL to the public
|
|
# wss:// base, or set OCPP_REQUIRE_TLS=false on a trusted network.
|
|
OCPP_REQUIRE_TLS=true
|
|
OCPP_PUBLIC_URL=
|
|
|
|
# --- Host port mappings (optional; defaults shown) --------------------------
|
|
WEB_PORT=8090
|
|
PB_PORT=8070
|
|
# API Server + its embedded web panel (served at the API root, http://host:8080/).
|
|
API_PORT=8080
|
|
|
|
# --- Build args (optional) ---------------------------------------------------
|
|
# Leave empty so the browser uses same-origin /api (proxied by nginx).
|
|
VITE_API_BASE=
|
|
# PocketBase version. The Dockerfile already pins one; set this only to build a
|
|
# different version. Leaving it commented out keeps the pin (an empty value here
|
|
# is passed through as-is and would resolve the latest release at build time).
|
|
#PB_VERSION=0.39.11
|
|
|
|
# --- 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 value below is re-applied on every restart and wins. Set it
|
|
# 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; nginx
|
|
# serves it on port 80 inside this container.
|
|
# CORS_ALLOW_ORIGINS browser origins allowed to call the API Server directly.
|
|
# WEBAPP_URL=http://127.0.0.1:80
|
|
|
|
# --- 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
|
|
# 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.
|
|
# 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
|
|
# SEAWEED_S3_PORT=8333
|
|
|
|
# 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.
|