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	332916e9db	Docker-AIO: PocketBase image with media in an external S3 bucket ... Dockerfile.PocketBase.s3 is the PocketBase all-in-one image with S3 turned on: media goes to an existing bucket on WARP_PB_S3_ENDPOINT (AWS, MinIO, or a SeaweedFS elsewhere), and the database stays in /data/pb_data. The compose files require the endpoint and key pair, default the bucket to warp, the region to us-east-1 and path style to true, and add host.docker.internal so the endpoint can be on the Docker host. Modelled on DriverVault's external-S3 compose files. The entrypoint now waits up to 30 seconds for an external S3 endpoint to answer and stops if it doesn't, instead of starting a homeserver that would fail on its first upload. WARP_PB_S3_FORCE_PATH_STYLE is left empty in .env.example so the S3 file's default applies. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-22 20:45:01 +02:00