tajniak81andClaude Opus 5
ee4ac441be
The project has no public installs, so there is nothing to migrate from. MigrateLegacyFile, the file-backed Store it read through, PLUGINS_FILE and the legacy path threaded through the Server all go. What is left is one store, PocketBase, and a plugins package that touches no filesystem at all. That was the last thing keeping api_data alive, so the volume goes too. All four compose files now declare exactly one volume, pb_data, and the standalone API Server compose declares none - it talks to an external PocketBase and has nothing of its own to keep. Backing up the stack is backing up one path again. Both images get simpler for it. The API Server image loses VOLUME /data and the su-exec entrypoint that existed only to fix a mounted volume's ownership, so it goes back to a plain USER app; its working directory is now /app and holds nothing. The AIO image loses its second volume and chowns only /pb/pb_data. One consequence worth stating plainly, because it is a small regression rather than a no-op. The panel's Settings -> PocketBase and Settings -> Web App screens write .env in the working directory, which is now ephemeral. In the multi-container stack that changes nothing: compose sets all five of those keys as container environment, and loadDotEnv only applies a key that is not already set, so the file could never win a restart there anyway. In the AIO image it did win for POCKETBASE_ADMIN_EMAIL/_PASSWORD, which are not in that container's environment - so a service account fixed from the panel now lasts only until the container is recreated. Both READMEs say so. Moving those two screens into the app_settings singleton would close it properly; the PocketBase URL and credentials cannot follow, since they are how the database is reached in the first place. go build, go vet and go test ./... pass; the compose files parse and each resolves to a single pb_data volume. Not verified: no Docker CLI here, so neither image was built. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
68 lines
3.4 KiB
Bash
68 lines
3.4 KiB
Bash
# DriverVault — production stack 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 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=
|
|
|
|
# --- 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.
|
|
PB_PORT=8070
|
|
PB_BIND=127.0.0.1
|
|
API_PORT=8080
|
|
API_BIND=127.0.0.1
|
|
|
|
# --- Storage -----------------------------------------------------------------
|
|
# Defaults are Docker-managed named volumes. To store either on a host path
|
|
# instead, set it to an absolute path, e.g. PB_DATA=/srv/drivervault/pb_data.
|
|
# PB_DATA — the PocketBase database and uploads. It is the only volume in the
|
|
# stack: the API Server keeps no state on disk, so everything it owns (plugin
|
|
# settings included) is backed up by backing up this one path.
|
|
PB_DATA=pb_data
|