2 Commits

Include renames

Author	SHA1	Message	Date
tajniak81andClaude Opus 5.5	66e48712c7	Docker, Docker-AIO: one .env example per compose file ... Replace each folder's shared .env.example with one example per compose file, named after it (docker-compose.<name>.yml takes .env.<name>.example), as DriverVault does. Each lists only the settings its compose file uses, names the required ones in its header, and the prod examples start from a public server name. Every variable a compose file substitutes is defined in its example. The compose headers point at their own example. The SeaweedFS files now fix WARP_PB_S3_REGION at us-east-1 instead of reading it from .env, since SeaweedFS ignores the region. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-22 21:00:44 +02:00
tajniak81andClaude Opus 5.5	36d83551aa	Docker-AIO: PocketBase images with SeaweedFS for media ... Dockerfile.PocketBase.SeaweedFS bakes SeaweedFS into the PocketBase all-in-one image as one `weed server -s3` process; Dockerfile.PocketBase.SeaweedFS.split runs master, volume, filer, S3 gateway and the admin UI as separate processes, with the homeserver's S3 identity seeded into the filer's IAM store on every boot. Media goes to the bucket, the database stays in /data/pb_data, and both layouts share /seaweed/data, so switching between them needs no migration. The entrypoint now tracks every process in one list and stops them in reverse start order, and it refuses to start an open S3 gateway or admin UI. Each image gets a build and a prod compose file, and .env.example and the README cover the new settings. Modelled on DriverVault's Docker-AIO SeaweedFS images. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-22 20:33:21 +02:00