Skip to content

fix: publie planning-api sur le port hôte 3001, pas 3000 #80

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
mortifia merged 1 commit into from
Jul 12, 2026
Merged

fix: publie planning-api sur le port hôte 3001, pas 3000 #80

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions docker-compose.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,8 +21,9 @@ services:
restart: unless-stopped
ports:
# Publié sur l'hôte car le CGI de Web_Planning tourne nativement sous Apache
# sur le VPS (pas dans un conteneur), il appelle donc http://localhost:3000.
- "3000:3000"
# sur le VPS (pas dans un conteneur), il appelle donc http://localhost:3001.
# 3001 et non 3000 : le port 3000 est déjà pris par le conteneur MillstoneSteam.
- "3001:3000"
volumes:
# events.xml + webhooks.json : données réelles, persistées hors du conteneur.
- ./api-data:/data
Loading