Hello, thanks for sharing this.
How would you suggest that site1 container should communicate with site2 container through proxy container? So that when I make an http request from site1's container to 'site2.example.com' it would route through reverse_proxy_proxy_1 container instead of going through the public internet.?
I would like to avoid using docker container names (e.g site1_web_1) since they are not valid urls and they cause problems in most web frameworks if used as host headers
Hello, thanks for sharing this.
How would you suggest that site1 container should communicate with site2 container through proxy container? So that when I make an http request from site1's container to 'site2.example.com' it would route through reverse_proxy_proxy_1 container instead of going through the public internet.?
I would like to avoid using docker container names (e.g site1_web_1) since they are not valid urls and they cause problems in most web frameworks if used as host headers