Files
Warp/Docker-AIO/docker-compose.sqlite.yml
T
tajniak81andClaude Opus 5.5 89f89b5d36 Docker-AIO: one image per database
Dockerfile builds warp-aio on SQLite, Dockerfile.PocketBase builds
warp-aio-pocketbase and Dockerfile.PostgreSQL builds warp-aio-postgresql
with PostgreSQL bundled. The database driver and connection string now
come from the image, so the SQLite and PocketBase images no longer carry
PostgreSQL (103 MB instead of 149 MB). The AIO compose files point at
their own Dockerfile and image, and the entrypoint refuses to start an
embedded PostgreSQL in an image that has none.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-22 20:22:24 +02:00

35 lines
961 B
YAML

# Warp all-in-one on SQLite: the homeserver, the admin panel and the web
# client in one container, built from this checkout.
#
# cd Docker-AIO
# cp .env.example .env # then edit it
# docker compose -f docker-compose.sqlite.yml up -d --build
#
# Homeserver http://localhost:8008, admin panel http://localhost:8009, web
# client http://localhost:8080. The database, signing key and media live
# in the warp-data volume.
#
# Create the first administrator once the server is up:
#
# docker compose -f docker-compose.sqlite.yml exec warp warp create-account --username admin --admin
name: warp-aio-sqlite
services:
warp:
build:
context: ..
dockerfile: Docker-AIO/Dockerfile
image: warp-aio:latest
restart: unless-stopped
env_file: .env
volumes:
- warp-data:/data
ports:
- "${WARP_PORT:-8008}:8008"
- "${WARP_ADMIN_PORT:-8009}:8009"
- "${WARP_WEB_PORT:-8080}:8080"
volumes:
warp-data: