Files
npm-statuspage/docker-compose.yml
Fredrik Johansson 0711a7f7ad
All checks were successful
Docker / build-and-push (push) Successful in 1m51s
Add pull_policy: always, matching wisp/keep's convention
Missed when the admin-panel work copied wisp's docker-compose.yml
pattern. Without it, `docker compose up -d` won't re-pull a new
:latest image if a container with the old one is already running —
the host's bulk deploy script (docker compose up -d per project, no
explicit pull step) would silently leave this project stale on every
redeploy.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-12 20:46:32 +02:00

22 lines
634 B
YAML

services:
app:
image: ${IMAGE}
restart: unless-stopped
pull_policy: always
ports:
- "${PORT:-3035}:3035"
environment:
- NPM_BASE_URL=${NPM_BASE_URL}
- NPM_EMAIL=${NPM_EMAIL}
- NPM_SECRET=${NPM_SECRET}
- NPM_INCLUDE_PATTERNS=${NPM_INCLUDE_PATTERNS}
# Admin UI (/admin) is disabled entirely if this is unset.
- ADMIN_PASSWORD=${ADMIN_PASSWORD}
volumes:
# Named volume, not a bind mount into the build context — the SQLite
# DB holding host overrides / manual targets must survive redeploys.
- statuspage-data:/app/data
volumes:
statuspage-data: