tajniak81andClaude Opus 5
01a8fecf40
Every deployment file advised setting PB_BOOTSTRAP=false "once the database
is established". That was harmless while the schema was static. It stopped
being harmless in 9bd5c52, which moved the plugin settings into a new
app_settings collection: a stack upgraded with the bootstrap off never gets
that collection, and a missing collection is deliberately read as "the
database is not ready" rather than "no plugins configured" - so the plugin
panel answers 503 indefinitely and the background retry spins forever.
Fixing the advice rather than the reading: treating a missing collection as
empty would let the first save write a fresh document over settings the
server had simply failed to find, which is the failure this whole line of
work exists to prevent.
So all four compose files, all four .env examples, both stack READMEs and
the AIO Dockerfile now say to leave the bootstrap on, including across
upgrades, and name the symptom an operator would otherwise have to guess
at. Turning it off is still supported, but framed as something to do only
for a database known to match the running release.
Compose files still parse as YAML; go build, go vet and go test ./... pass
(untouched by this commit - it is comments and docs only). Note that this
is guidance, not a guard: an operator who sets PB_BOOTSTRAP=false anyway
still ends up in the same place, and the server would have to re-run the
bootstrap when it finds the collection missing to make that impossible.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
55 lines
2.5 KiB
Bash
55 lines
2.5 KiB
Bash
# DriverVault all-in-one — production config.
|
|
# Copy to .env and fill in, then:
|
|
# docker compose -f docker-compose.prod.yml pull
|
|
# docker compose -f docker-compose.prod.yml up -d
|
|
|
|
# --- Registry image ----------------------------------------------------------
|
|
AIO_IMAGE=10.2.1.10:5500/admin/drivervault-aio:latest
|
|
|
|
# --- PocketBase superuser (required) -----------------------------------------
|
|
# Created/updated on first boot. The API Server uses these to manage the database.
|
|
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 a
|
|
# collection the server needs (app_settings, which holds the plugin settings),
|
|
# and a stack that skipped the bootstrap never gets it — the plugin panel then
|
|
# answers 503 forever. Set false only for a database you know matches the release.
|
|
PB_BOOTSTRAP=true
|
|
|
|
# Allowed CORS origin(s) — match your public web URL / 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, so
|
|
# terminate TLS in a reverse proxy in front of it and set OCPP_PUBLIC_URL to the
|
|
# public wss:// base the charger should be pointed at. Turning the check off is
|
|
# for trusted networks only.
|
|
OCPP_REQUIRE_TLS=true
|
|
OCPP_PUBLIC_URL=
|
|
|
|
# --- Host port mappings (optional; defaults shown) --------------------------
|
|
WEB_PORT=8090
|
|
PB_PORT=8070
|
|
API_PORT=8080
|
|
|
|
# --- Storage -----------------------------------------------------------------
|
|
# Defaults are Docker-managed named volumes. Set either to an absolute host path
|
|
# for a bind mount, e.g. PB_DATA=/srv/drivervault/pb_data.
|
|
# PB_DATA — the PocketBase database and uploads.
|
|
# API_DATA — the .env the API Server panel writes back (plugin settings are in
|
|
# the database, under PB_DATA)
|
|
# when a superadmin retargets the PocketBase connection.
|
|
PB_DATA=pb_data
|
|
API_DATA=api_data
|