In my project I have a constraint where I have to whitelist some IP for a reverse proxy to a specific url
/system However I wanted to have the root path be on the App Platform so I can make use of Zero Downtime Deploys and CD, high availability etc. So on the droplet I made a reverse proxy from nginx to the URL generated from the App platform. Everything is working fine, but still I wanted to ask if this is something I could do? Can this have drawbacks in the future? I realise that I will be billed based on the bandwidth on the app platform and not the droplet and that is ok.
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Click below to sign up and get $200 of credit to try our products over 60 days!
Seems reasonable to me. Dedicated egress IPs are something that we have on the roadmap though it’s a ton of work and will take some time.
As for downsides, I guess there may be a tiny bit of added latency. The biggest drawback will be maintaining that Nginx proxy.
Hope this helps!