chore: add a unified Docker network for all Huly services #197
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
Previously, each service was relying on the default Docker Compose network. As a result, cross-container communication (e.g., transactor → redpanda) failed, causing KafkaJS connection timeouts and WebSocket session errors. This commit introduces a shared network 'huly_net' and attaches all services to it, allowing reliable service discovery by container names. The Docker and Docker Compose versions mentioned below are the versions used in the current working environment: - Docker version: 28.3.3 - Docker Compose version: v2.39.1 Changes: - All services now use network: huly_net - Network is defined at the bottom of the Compose file - Container names remain unchanged - Healthchecks and ports are untouched Signed-off-by: _DiSay <[email protected]>
|
Connected to Huly®: SELFH-196 |
shanzez
approved these changes
Sep 1, 2025
aonnikov
approved these changes
Sep 8, 2025
|
Thanks for your contribution! Looks good to me, but could you please resolve conflicts when you have a chance? |
lexiv0re
requested changes
Sep 8, 2025
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.
Previously, each service was relying on the default Docker Compose network. As a result, cross-container communication (e.g., transactor → redpanda) failed, causing KafkaJS connection timeouts and WebSocket session errors.
This commit introduces a shared network 'huly_net' and attaches all services to it, allowing reliable service discovery by container names.
The Docker and Docker Compose versions mentioned below are the versions used in the current working environment:
Changes: