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>
42 lines
1.4 KiB
YAML
42 lines
1.4 KiB
YAML
# Warp all-in-one on PocketBase: the homeserver, the admin panel and the
|
|
# web client in one container, built from this checkout.
|
|
#
|
|
# cd Docker-AIO
|
|
# cp .env.pocketbase.example .env # then edit it
|
|
# docker compose -f docker-compose.pocketbase.yml up -d --build
|
|
#
|
|
# PocketBase runs in the container as a server of its own, which the
|
|
# homeserver signs in to as the superuser in .env (or one the container
|
|
# makes up, kept in /data/pocketbase-superuser.env): its pb_data, with media
|
|
# in its storage, is /data/pb_data in the warp-data volume. Its admin UI is
|
|
# http://localhost:8070/_/ on loopback. Set WARP_PB_S3_* in .env to keep media in an
|
|
# S3 bucket instead (docs/configuration.md).
|
|
#
|
|
# Homeserver http://localhost:8008, admin panel http://localhost:8009, web
|
|
# client http://localhost:8080.
|
|
#
|
|
# Create the first administrator once the server is up:
|
|
#
|
|
# docker compose -f docker-compose.pocketbase.yml exec warp warp create-account --username admin --admin
|
|
|
|
name: warp-aio-pocketbase
|
|
|
|
services:
|
|
warp:
|
|
build:
|
|
context: ..
|
|
dockerfile: Docker-AIO/Dockerfile.PocketBase
|
|
image: warp-aio-pocketbase:latest
|
|
restart: unless-stopped
|
|
env_file: .env
|
|
volumes:
|
|
- ${WARP_DATA_VOLUME:-warp-data}:/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"
|
|
|
|
volumes:
|
|
warp-data:
|