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
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