Install migration proxy#44
Merged
Merged
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.
This swaps up the network path for mail services such that the public interface is now aimed at the Stalwart migration proxy. This is configured for the moment with only one backend, called
tb-dev/prod-thundermail, which uses that domain and cert to intercept and route traffic. The migration proxy's destination is the nginx proxy, which denies access to certain endpoints. Mail ports and allowed HTTP paths are correctly routed to the Stalwart backend. Public access to nginx has been cut off. All traffic must flow through the Stalwart proxy.