tajniak81andClaude Opus 5.5
0994156705
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>
39 lines
1.3 KiB
YAML
39 lines
1.3 KiB
YAML
# Warp all-in-one on SQLite: the homeserver, the admin panel and the web
|
|
# client in one container, pulled from a registry.
|
|
#
|
|
# cd Docker-AIO
|
|
# cp .env.sqlite.prod.example .env # then edit it
|
|
# docker compose -f docker-compose.sqlite.prod.yml up -d
|
|
#
|
|
# 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.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.sqlite.prod.yml pull && docker compose -f docker-compose.sqlite.prod.yml up -d
|
|
|
|
name: warp-aio-sqlite
|
|
|
|
services:
|
|
warp:
|
|
image: ${WARP_REGISTRY:-10.2.1.10:5500/admin}/warp-aio:${WARP_VERSION:-latest}
|
|
pull_policy: always
|
|
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:
|