feat: connect Finance services to platform edge - #5
Merged
Conversation
iPior
marked this pull request as ready for review
July 12, 2026 04:47
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
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.
Summary
pior_edgenetwork asfinance-webpior_edgeasfinance-apiWhy
The containerized platform Caddy routes Finance traffic to
finance-web:80andfinance-api:3000. Those aliases must exist on the shared edge network before Finance can be tested through the new Caddy instance.Impact
The current host-Caddy deployment remains operational because the existing
127.0.0.1:8080web binding and127.0.0.1:3000API binding are retained. This PR only adds a second, private Docker-network path for the test edge proxy.Validation after merge
Expected behavior:
/api/*are routed to the API container