tajniak81andClaude Opus 5
9a2a4ab72e
Every attachment — a document scan, a fuel receipt, a workshop invoice, a
photo of a part's box — has lived inside pb_data, in a directory beside the
SQLite file. One volume held both, so neither could be sized, backed up or
moved without the other. PocketBase can keep those bytes in an S3 bucket
instead, and now it is told to.
Nothing on the way to a client changes, because an attachment was never a
storage URL to begin with: it is fetched from GET /api/{records}/{id}/file,
which re-checks car access and asks PocketBase for the bytes as the service
account. PocketBase streams from the bucket through that same endpoint rather
than redirecting to it, so the web app, the phone and the plugin cannot tell
which side of the switch they are on.
The bootstrap that already creates the collections now writes PocketBase's
files-storage settings too, from PB_S3_*, on every boot and only when they
differ from what is already there — then asks PocketBase to prove it can reach
the bucket, and says so in the log either way. Two asymmetries are deliberate.
A read of the settings masks the stored secret, so a rotation of the secret
alone is invisible from here and needs another PB_S3_* to move with it. And it
never turns S3 back off: files already written to a bucket are reachable only
while PocketBase still points at it, so dropping the configuration would strand
them rather than undo anything.
Each deployment shape is one compose file with an .env example of the same
name, not a base plus an overlay to remember — six of each per folder, for
Docker and Docker-AIO alike: the plain one, .seaweedfs, .s3, and the three prod
twins. The SeaweedFS files run master, volume, filer and gateway as one process
and a one-shot init container beside it, because PocketBase never issues a
CreateBucket and SeaweedFS will not conjure one on first upload. The credentials
do double duty there — the gateway's only identity is also what PocketBase
authenticates with. In the all-in-one that gateway is a second container rather
than a fourth process under supervisord: keeping the object store inside the
image, on the volume the files are being moved off, would have defeated the
point and would have meant rebuilding.
Files uploaded before the switch are not carried across; PocketBase copies
nothing, and both READMEs say so where an operator will read it.
The TLS overlay and its Caddyfile go. The section they served stays, without
them: nothing in the stack terminates TLS any more, so it now names the four
variables to set in front of whichever proxy already does — TRUST_FORWARDED_PROTO
being the one that decides whether a charger is believed about how it arrived.
Unexercised: this was written on a machine without Docker, so the pinned
SeaweedFS image, the bucket-create and the settings write have not been run
against a live stack. The Go side builds, vets and tests clean.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
80 lines
4.0 KiB
Bash
80 lines
4.0 KiB
Bash
# Copy to .env and fill in. Used by the Docker-AIO docker-compose.s3.yml.
|
|
|
|
# --- 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: external S3 -----------------------------------------------
|
|
# 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.
|
|
#
|
|
# Nothing in this stack runs a gateway: both the endpoint and the bucket must
|
|
# already exist. For a gateway on this Docker host use
|
|
# http://host.docker.internal:8333 — the compose file adds the host entry that
|
|
# makes that name resolve inside the containers.
|
|
PB_S3_ENDPOINT=http://host.docker.internal:8333
|
|
PB_S3_BUCKET=drivervault
|
|
PB_S3_ACCESS_KEY=
|
|
PB_S3_SECRET=
|
|
# SeaweedFS and MinIO ignore the region; PocketBase insists on having one.
|
|
PB_S3_REGION=us-east-1
|
|
# true for SeaweedFS and MinIO, false for AWS S3 proper.
|
|
PB_S3_FORCE_PATH_STYLE=true
|
|
|
|
# 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.
|