NoiceHax
a40b418038
TWO_FACTOR_ENCRYPTION_KEY has no default, so instances upgrading to 3.3 without setting it hit an unhandled throw from encryptSecret: the setup dialog only reported "Something went wrong", and where 2FA was required the blocking dialog made the whole app unusable. The status endpoint now reports 2FA as not required while the key is missing or invalid, and setup initiation returns 503 with a two-factor-error-not-configured code that the setup dialog renders as a readable message. Also documents the variable in the README and the example compose file. Closes #4443
38 lines
1016 B
YAML
38 lines
1016 B
YAML
---
|
|
services:
|
|
umami:
|
|
image: ghcr.io/umami-software/umami:latest
|
|
ports:
|
|
- "3000:3000"
|
|
environment:
|
|
DATABASE_URL: postgresql://umami:umami@db:5432/umami
|
|
APP_SECRET: replace-me-with-a-random-string
|
|
# Required for two-factor authentication, generate with: openssl rand -hex 32
|
|
TWO_FACTOR_ENCRYPTION_KEY: replace-me-with-a-64-character-hex-string
|
|
depends_on:
|
|
db:
|
|
condition: service_healthy
|
|
init: true
|
|
restart: always
|
|
healthcheck:
|
|
test: ["CMD-SHELL", "curl http://localhost:3000/api/heartbeat"]
|
|
interval: 5s
|
|
timeout: 5s
|
|
retries: 5
|
|
db:
|
|
image: postgres:15-alpine
|
|
environment:
|
|
POSTGRES_DB: umami
|
|
POSTGRES_USER: umami
|
|
POSTGRES_PASSWORD: umami
|
|
volumes:
|
|
- umami-db-data:/var/lib/postgresql/data
|
|
restart: always
|
|
healthcheck:
|
|
test: ["CMD-SHELL", "pg_isready -U $${POSTGRES_USER} -d $${POSTGRES_DB}"]
|
|
interval: 5s
|
|
timeout: 5s
|
|
retries: 5
|
|
volumes:
|
|
umami-db-data:
|