Files
Warp/Docker-AIO/docker-compose.sqlite.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

35 lines
989 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.sqlite.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_VOLUME:-warp-data}:/data
ports:
- "${WARP_PORT:-8008}:8008"
- "${WARP_ADMIN_PORT:-8009}:8009"
- "${WARP_WEB_PORT:-8080}:8080"
volumes:
warp-data: