tajniak81andClaude Opus 5.5
a47e15cc1c
CI / Test (ubuntu-latest) (push) Canceled after 0s
CI / Test (windows-latest) (push) Canceled after 0s
CI / Storage tests on PostgreSQL (push) Canceled after 0s
CI / Complement (federation off) (push) Canceled after 0s
CI / golangci-lint (push) Canceled after 0s
CI / Smoke test the binary (push) Canceled after 0s
CI / Admin panel (push) Canceled after 0s
CI / Web client (push) Canceled after 0s
CI / Desktop client (ubuntu-24.04) (push) Canceled after 0s
CI / Desktop client (windows-latest) (push) Canceled after 0s
The pocketbase driver no longer embeds PocketBase: Warp keeps its data as PocketBase collections on a server of its own and reaches it only through the REST API, the way the postgres driver reaches PostgreSQL. database.connection_string is the server's URL, and Warp signs in as the superuser in WARP_PB_SUPERUSER_EMAIL / WARP_PB_SUPERUSER_PASSWORD (or a WARP_PB_SUPERUSER_FILE of the two). Every SQL table is a superuser-only collection of the same name and columns, created by warp migrate. Reads go through PocketBase's SQL endpoint with the SQL drivers' queries, via a read-only database/sql driver that inlines arguments, moves long ones into warp_params and pages past 1000 rows. Writes are record operations in batch requests under one write lock in the Warp process. Media is a protected file field in warp_media, local or in the S3 bucket Warp writes into PocketBase's settings. Search matches word prefixes with LIKE. The storage tests run against an in-process PocketBase and pass as on SQLite. Docker: the PocketBase stacks get a pocketbase service running tajniak81/pocketbase-docker-root (WARP_PB_IMAGE), with a pb-data volume and its admin UI on loopback; the AIO images run that PocketBase binary as a process beside the homeserver, making up a superuser when none is set. The .env examples, READMEs, docs and warp.yaml.example follow. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
66 lines
2.9 KiB
YAML
66 lines
2.9 KiB
YAML
# Warp all-in-one on PocketBase with SeaweedFS: the homeserver, the admin
|
|
# panel, the web client and SeaweedFS (one `weed server -s3` process) in one
|
|
# container pulled from a registry (the image is built from
|
|
# Dockerfile.PocketBase.SeaweedFS).
|
|
#
|
|
# cd Docker-AIO
|
|
# cp .env.pocketbase.seaweedfs.prod.example .env # then edit it
|
|
# docker compose -f docker-compose.pocketbase.seaweedfs.prod.yml up -d
|
|
#
|
|
# PocketBase runs in the container, its database in /data/pb_data
|
|
# (warp-data), admin UI on loopback at http://localhost:8070/_/; media goes to the bucket
|
|
# WARP_PB_S3_BUCKET in SeaweedFS (seaweed-data), whose gateway has exactly
|
|
# one identity: the homeserver's. 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) is published on
|
|
# loopback, for aws-cli and the like; SEAWEED_S3_BIND=0.0.0.0 exposes it.
|
|
#
|
|
# This and docker-compose.pocketbase.seaweedfs.split.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.prod.yml exec warp warp create-account --username admin --admin
|
|
#
|
|
# Nothing is built here: the image comes from WARP_REGISTRY (default
|
|
# 10.2.1.10:5500/admin) at tag WARP_VERSION (default latest). Pin
|
|
# WARP_VERSION to a release in production, and update with
|
|
#
|
|
# docker compose -f docker-compose.pocketbase.seaweedfs.prod.yml pull && docker compose -f docker-compose.pocketbase.seaweedfs.prod.yml up -d
|
|
|
|
name: warp-aio-pocketbase-seaweedfs
|
|
|
|
services:
|
|
warp:
|
|
image: ${WARP_REGISTRY:-10.2.1.10:5500/admin}/warp-aio-pocketbase-seaweedfs:${WARP_VERSION:-latest}
|
|
pull_policy: always
|
|
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 gateway's only identity, and what the homeserver 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}
|
|
volumes:
|
|
- ${WARP_DATA_VOLUME:-warp-data}:/data
|
|
- ${SEAWEED_DATA_VOLUME:-seaweed-data}:/seaweed/data
|
|
ports:
|
|
- "${WARP_PORT:-8008}:8008"
|
|
- "${WARP_ADMIN_PORT:-8009}:8009"
|
|
- "${WARP_WEB_PORT:-8080}:8080"
|
|
- "${WARP_PB_BIND:-127.0.0.1}:${WARP_PB_PORT:-8070}:8070"
|
|
- "${SEAWEED_S3_BIND:-127.0.0.1}:${SEAWEED_S3_PORT:-8333}:8333"
|
|
|
|
volumes:
|
|
warp-data:
|
|
seaweed-data:
|