chore(docker): make host ports customizable via environment variables#452
Open
ducconit wants to merge 1 commit intonextlevelbuilder:mainfrom
Open
chore(docker): make host ports customizable via environment variables#452ducconit wants to merge 1 commit intonextlevelbuilder:mainfrom
ducconit wants to merge 1 commit intonextlevelbuilder:mainfrom
Conversation
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.
🎯 Changes
This pull request modifies the Docker Compose configurations to allow host ports to be configurable via environment variables instead of being hardcoded.
${JAEGER_UI_PORT:-16686},${OTLP_GRPC_PORT:-4317}, and${OTLP_HTTP_PORT:-4318}for observability services.${REDIS_PORT:-6379}for the Redis service.💡 Motivation
Hardcoded port mappings can often lead to port conflicts on host machines, especially in environments running multiple stack instances or standard local services. This standardizes the compose overlays to match the current pattern, making deployments much more flexible and adaptable avoiding conflicts out-of-the-box.
✅ Checklist