Using published images in dockerhub #1
Conversation
This file contains 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
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.
@aitrusgit tengo una única duda, el cambio de puerto en el front.
Intenté levantar el compose así como estaba, contra las imágenes buildeadas por travis desde el branch "dockerized" de cada módulo (front y back), y pasaba que al pegarle a localhost:8080 (traeffik), me tiraba bad gateway.
Mirando el log del compose, veía que el front levantaba en el 5000 y no en el 3000 como estaba configurado traeffik, así que lo cambié.
No se si es que el compose laburaba contra el front en modo webpack (wds) y eso era puerto 3000, pero ahora con "serve" usa el 5000 ?
En fin.. se te ocurre algún motivo para no hacer este cambio ?