Files
Warp/Docker-AIO/docker-compose.pocketbase.seaweedfs.split.yml
T
tajniak81andClaude Opus 5.5 0994156705 Docker, Docker-AIO: private registry, data volumes set from .env
Images now default to the registry 10.2.1.10:5500/admin instead of
ghcr.io/dariuszjaniak, in the compose files, the .env examples and the
READMEs.

Each data volume's source comes from .env: WARP_DATA_VOLUME,
WARP_POSTGRES_VOLUME, SEAWEED_DATA_VOLUME and SEAWEED_ADMIN_VOLUME.
Empty keeps the named volume; a host path bind-mounts that directory,
which must be writable by UID 10001 where the homeserver or the AIO
container uses it. Each .env example lists the ones its compose file
mounts.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-26 14:46:31 +01:00

75 lines
3.4 KiB
YAML

# Warp all-in-one on PocketBase with SeaweedFS split into its roles: the
# homeserver, the admin panel, the web client, and SeaweedFS's master,
# volume, filer, S3 gateway and admin UI, all in one container built from
# this checkout (Dockerfile.PocketBase.SeaweedFS.split).
#
# cd Docker-AIO
# cp .env.pocketbase.seaweedfs.split.example .env # then edit it
# docker compose -f docker-compose.pocketbase.seaweedfs.split.yml up -d --build
#
# The database stays in /data/pb_data (warp-data); media goes to the bucket
# WARP_PB_S3_BUCKET in SeaweedFS (seaweed-data). The homeserver's S3 identity
# is seeded into the filer's IAM store on every boot, beside any added in
# the admin UI under Object Store → Users. Media stored before S3 was on is
# not moved into the bucket.
#
# Homeserver http://localhost:8008, admin panel http://localhost:8009, web
# client http://localhost:8080. The S3 gateway (8333) and the SeaweedFS admin
# UI (23646) are published on loopback; SEAWEED_S3_BIND and
# SEAWEED_ADMIN_BIND=0.0.0.0 expose them, the admin UI only behind a proxy.
#
# This and docker-compose.pocketbase.seaweedfs.yml share their project and
# volumes: SeaweedFS's data has the same layout either way, so switching
# between them needs no migration.
#
# Create the first administrator once the server is up:
#
# docker compose -f docker-compose.pocketbase.seaweedfs.split.yml exec warp warp create-account --username admin --admin
name: warp-aio-pocketbase-seaweedfs
services:
warp:
build:
context: ..
dockerfile: Docker-AIO/Dockerfile.PocketBase.SeaweedFS.split
args:
# Passed only when set, so the Dockerfile's pin stays otherwise.
- SEAWEED_VERSION
image: warp-aio-pocketbase-seaweedfs-split:latest
restart: unless-stopped
env_file: .env
environment:
# The gateway is in the container at a fixed address; these override
# whatever .env says about S3.
WARP_PB_S3_ENABLED: "true"
WARP_PB_S3_ENDPOINT: http://127.0.0.1:8333
WARP_PB_S3_BUCKET: ${WARP_PB_S3_BUCKET:-warp}
WARP_PB_S3_REGION: us-east-1 # SeaweedFS ignores it; the client wants one
WARP_PB_S3_FORCE_PATH_STYLE: "true"
# The homeserver's identity in SeaweedFS, and what it signs with.
WARP_PB_S3_ACCESS_KEY: ${WARP_PB_S3_ACCESS_KEY:?set WARP_PB_S3_ACCESS_KEY in .env}
WARP_PB_S3_SECRET: ${WARP_PB_S3_SECRET:?set WARP_PB_S3_SECRET in .env}
# The admin UI can mint bucket credentials, so it needs a password.
WEED_ADMIN_USER: ${SEAWEED_ADMIN_USER:-admin}
WEED_ADMIN_PASSWORD: ${SEAWEED_ADMIN_PASSWORD:?set SEAWEED_ADMIN_PASSWORD in .env}
WEED_ADMIN_READONLY_USER: ${SEAWEED_ADMIN_READONLY_USER:-}
WEED_ADMIN_READONLY_PASSWORD: ${SEAWEED_ADMIN_READONLY_PASSWORD:-}
volumes:
- ${WARP_DATA_VOLUME:-warp-data}:/data
- ${SEAWEED_DATA_VOLUME:-seaweed-data}:/seaweed/data
- ${SEAWEED_ADMIN_VOLUME:-seaweed-admin}:/seaweed/admin
ports:
- "${WARP_PORT:-8008}:8008"
- "${WARP_ADMIN_PORT:-8009}:8009"
- "${WARP_WEB_PORT:-8080}:8080"
- "${SEAWEED_S3_BIND:-127.0.0.1}:${SEAWEED_S3_PORT:-8333}:8333"
- "${SEAWEED_ADMIN_BIND:-127.0.0.1}:${SEAWEED_ADMIN_PORT:-23646}:23646"
volumes:
warp-data:
# Master, volume and filer share it, as `weed server -dir` lays it out.
seaweed-data:
# The admin UI's session key and maintenance state; no object data.
seaweed-admin: