Cantaloupe reverse proxy using resolver #3
Closed
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.
This adds the reverse proxy to Cantaloupe based on using an external (to the nginx process / the container) to look up the IP address of the Cantaloupe server. The nginx config is currently configured to use the Quad9 resolver, but this can/should be changed before deploy as per the IA's preferences.
Pro: Cantaloupe can be freely moved around (e.g on and off load balancer, to a different load balancer, to an internal-only domain, etc).
Con: Due to quirks in how nginx works, the target domain will be re-resolved on every request -> more traffic
NB: Only one of this or #2 should be merged, followed by #4 to update the address used in manifest generation