Files
Presencia/docker-compose.yml
T
Claude 2170489424 Fix: aligner PGPASSWORD (backend) sur POSTGRES_PASSWORD (db)
Le précédent remplacement du mot de passe Postgres n'avait touché que
la clé POSTGRES_PASSWORD du service db, laissant le backend avec
l'ancien mot de passe sous la clé PGPASSWORD — cause de l'échec
d'authentification systématique malgré la réinitialisation du volume.
2026-07-06 09:10:48 +00:00

55 lines
1.1 KiB
YAML

services:
db:
image: postgres:16-alpine
restart: unless-stopped
environment:
POSTGRES_USER: presencia
POSTGRES_PASSWORD: R4dsITu0vuigNQQwNlvj0agVyHupSyX
POSTGRES_DB: presencia
volumes:
- presencia_pgdata:/var/lib/postgresql/data
ports:
- "6543:5432"
healthcheck:
test: ["CMD-SHELL", "pg_isready -U presencia"]
interval: 5s
timeout: 5s
retries: 10
backend:
build: ./backend
restart: unless-stopped
depends_on:
db:
condition: service_healthy
environment:
PORT: 4790
PGHOST: db
PGPORT: 5432
PGUSER: presencia
PGPASSWORD: R4dsITu0vuigNQQwNlvj0agVyHupSyX
PGDATABASE: presencia
JWT_SECRET: change-me-to-a-long-random-string
COOKIE_SECURE: "false"
ADMIN_EMAIL: michaelschal@ffest.fr
ADMIN_PASSWORD: Lapîn2509
ADMIN_NAME: Michael
ports:
- "4790:4790"
frontend:
build: ./frontend
restart: unless-stopped
depends_on:
- backend
ports:
- "8781:80"
networks:
default:
name: nginx_default
external: true
volumes:
presencia_pgdata: