Docker/ gets the same deployment shapes as DriverVault: plain, SeaweedFS in the stack, SeaweedFS split into its roles, and an external S3 endpoint, each as a build-from-source and a registry compose file with an .env example of the same name, plus a README. The API Server now reads PB_S3_* on boot and points PocketBase's file storage at the bucket (only when the settings differ), then asks PocketBase to test it. It never turns S3 off. Plugin state gets an api_data volume, since the image could not write plugins.json. The PocketBase image pinned v0.22.21, which cannot run the v0.23+ migrations or `superuser upsert`; it now pins v0.39.11. Starting from an empty database also exposed two migration bugs: the seed tried to create a passwordless account, and the documents collection saved its self-relation with a blank target. Both are fixed; databases that already ran them are unaffected. Verified on Docker: the SeaweedFS and split stacks come up healthy from an empty database, uploads land in the bucket, and a restart is a no-op. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
30 lines
638 B
Plaintext
30 lines
638 B
Plaintext
# Root build-context ignore. The pocketbase and Docker AIO images build with the
|
|
# repo root as their context (they COPY from "API Server/" and "Web App/"), so
|
|
# keep the context lean: only those two trees plus Docker/pocketbase are needed.
|
|
|
|
# Sibling apps unrelated to the server images.
|
|
Adobe Plugin/
|
|
Design/
|
|
Fly App/
|
|
Fly 2 App/
|
|
Fly Agent App/
|
|
Phone App/
|
|
|
|
# Frontend deps + generated bundles — rebuilt inside the images.
|
|
**/node_modules/
|
|
**/dist/
|
|
|
|
# Secrets & local build artifacts — never send to the build context.
|
|
**/.env
|
|
plugins.json
|
|
*.exe
|
|
*.exe~
|
|
*.log
|
|
|
|
# VCS / editor / tooling noise.
|
|
.git/
|
|
.gitignore
|
|
.claude/
|
|
.vscode/
|
|
.idea/
|