Files
SealShare/docker-compose.yml
T
Andreas Reinhold / reiniandClaude Opus 5 c1906d2009 Stop the SQLite volume from hiding new migrations
Uploads on share.kadenpartner.ch failed with 409 on every chunk after
the update to 2.1. The example docker-compose.yml mounts the SQLite
volume over all of /app/database. Docker fills a volume from the image
only when it is created, so the container kept the 2.0 migrations and
never saw the 2.1 one. share_files.uploaded_chunks was never created,
so the chunk endpoint read null and answered 409. SQLite takes the
unknown "completed_at" in whereNull() as a string, so nothing failed
earlier.

- The image keeps a copy of its migrations in docker/migrations. On
  startup the entrypoint adds the ones missing from database/migrations
  before migrating, so installs with the old mount recover by pulling
  the new image.
- docker-compose.example.yml and docker-compose.yml mount
  sealshare_database at /app/database/sqlite and set DB_DATABASE to the
  file in it. An existing volume can be moved there without losing
  data: its database.sqlite lands at exactly that path.
- Tested with a locally built image: a volume created by 2.0.1 with the
  old mount gets the migration once (not again on restart) and keeps
  its settings; the same volume moved to the new path keeps its data;
  a fresh volume with the new layout starts healthy.
- README and CHANGELOG (Unreleased) describe the new path and how to
  switch.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-09-17 10:53:27 +02:00

82 lines
2.6 KiB
YAML

services:
app:
image: gitea.nonameweb.ch/nonameweb/sealshare:latest
build:
context: .
dockerfile: Dockerfile
restart: unless-stopped
ports:
- "80:80"
- "443:443"
- "443:443/udp"
volumes:
- sealshare_storage:/app/storage/app
- sealshare_database:/app/database/sqlite
- caddy_data:/data
- caddy_config:/config
environment:
APP_KEY: ${APP_KEY:?Set APP_KEY in .env or environment}
APP_URL: ${APP_URL:-http://localhost}
APP_ENV: ${APP_ENV:-production}
APP_DEBUG: ${APP_DEBUG:-false}
AUTO_HTTPS: ${AUTO_HTTPS:-false}
SERVER_NAME: ${SERVER_NAME:-localhost}
DB_CONNECTION: ${DB_CONNECTION:-sqlite}
DB_HOST: ${DB_HOST:-}
DB_PORT: ${DB_PORT:-}
DB_DATABASE: ${DB_DATABASE:-/app/database/sqlite/database.sqlite}
DB_USERNAME: ${DB_USERNAME:-}
DB_PASSWORD: ${DB_PASSWORD:-}
LOG_CHANNEL: ${LOG_CHANNEL:-stderr}
LOG_LEVEL: ${LOG_LEVEL:-warning}
SESSION_DRIVER: ${SESSION_DRIVER:-database}
QUEUE_CONNECTION: ${QUEUE_CONNECTION:-database}
CACHE_STORE: ${CACHE_STORE:-database}
OCTANE_HTTPS: ${OCTANE_HTTPS:-false}
OCTANE_MAX_EXECUTION_TIME: ${OCTANE_MAX_EXECUTION_TIME:-300}
UPLOAD_CHUNK_SIZE_MB: ${UPLOAD_CHUNK_SIZE_MB:-16}
PHP_UPLOAD_MAX_FILESIZE: ${PHP_UPLOAD_MAX_FILESIZE:-64M}
PHP_POST_MAX_SIZE: ${PHP_POST_MAX_SIZE:-64M}
PHP_MAX_EXECUTION_TIME: ${PHP_MAX_EXECUTION_TIME:-300}
PHP_MAX_INPUT_TIME: ${PHP_MAX_INPUT_TIME:-300}
PHP_MEMORY_LIMIT: ${PHP_MEMORY_LIMIT:-512M}
healthcheck:
test: ["CMD", "/app/docker/healthcheck.sh"]
interval: 30s
timeout: 5s
start_period: 10s
retries: 3
scheduler:
image: gitea.nonameweb.ch/nonameweb/sealshare:latest
build:
context: .
dockerfile: Dockerfile
restart: unless-stopped
entrypoint: ["php", "artisan", "schedule:work"]
volumes:
- sealshare_storage:/app/storage/app
- sealshare_database:/app/database/sqlite
environment:
APP_KEY: ${APP_KEY:?Set APP_KEY in .env or environment}
APP_URL: ${APP_URL:-http://localhost}
APP_ENV: ${APP_ENV:-production}
APP_DEBUG: ${APP_DEBUG:-false}
DB_CONNECTION: ${DB_CONNECTION:-sqlite}
DB_HOST: ${DB_HOST:-}
DB_PORT: ${DB_PORT:-}
DB_DATABASE: ${DB_DATABASE:-/app/database/sqlite/database.sqlite}
DB_USERNAME: ${DB_USERNAME:-}
DB_PASSWORD: ${DB_PASSWORD:-}
LOG_CHANNEL: ${LOG_CHANNEL:-stderr}
LOG_LEVEL: ${LOG_LEVEL:-warning}
depends_on:
app:
condition: service_healthy
volumes:
sealshare_storage:
sealshare_database:
caddy_data:
caddy_config: