fix: publie planning-api sur le port hôte 3001, pas 3000#80
Merged
Conversation
Le port 3000 est déjà occupé par le conteneur MillstoneSteam (app) sur le VPS. Le port interne du conteneur (3000) est inchangé, seul le mapping hôte change.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Découvert au déploiement de #79 : le port 3000 est déjà pris par le conteneur MillstoneSteam (
app) sur le VPS,docker compose upéchouait ("port is already allocated"). Seul le port publié côté hôte change, le port interne du conteneur reste 3000.