PocketBase as a standalone database server
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>
This commit is contained in:
tajniak81andClaude Opus 5.5 committed 2026-10-26 16:31:08 +01:00
1 parent 0994156705
commit a47e15cc1c
69 files changed
+8209 -374

No files matched your search

+11 -6
View File
@@ -51,13 +51,13 @@ listen:
database:
# sqlite (dev, single user), postgres (production) or pocketbase
# (appliance: sqlite inside an embedded PocketBase, media on its
# filesystem, local or S3). WARP_DB_DRIVER
# (a PocketBase server of its own, media in its storage, local or
# S3). WARP_DB_DRIVER
driver: sqlite
# sqlite: file:warp.db?_pragma=journal_mode(WAL)
# postgres: postgres://warp:secret@localhost/warp?sslmode=disable
# pocketbase: the data directory, e.g. ./pb_data
# pocketbase: the server's URL, e.g. http://localhost:8070
# WARP_DB_CONNECTION_STRING
connection_string: "file:warp.db?_pragma=journal_mode(WAL)&_pragma=busy_timeout(10000)&_pragma=foreign_keys(1)"
@@ -69,10 +69,15 @@ database:
# behind an explicit `warp migrate`. WARP_DB_AUTO_MIGRATE
auto_migrate: true
# The pocketbase driver only. With S3 on, media content goes to the
# bucket instead of <data directory>/storage; media.base_path is not
# used by this driver either way.
# The pocketbase driver only. Warp signs in as this PocketBase
# superuser. With S3 on, media content goes to the bucket instead of
# PocketBase's pb_data/storage, and Warp writes the bucket into
# PocketBase's settings on every start; media.base_path is not used by
# this driver either way.
pocketbase:
superuser_email: "" # WARP_PB_SUPERUSER_EMAIL
superuser_password: "" # WARP_PB_SUPERUSER_PASSWORD
superuser_file: "" # WARP_PB_SUPERUSER_FILE: KEY=value lines for either
s3:
enabled: false # WARP_PB_S3_ENABLED
bucket: "" # WARP_PB_S3_BUCKET