Closed viju2008 closed 7 months ago
We have created an issue in Pivotal Tracker to manage this. Unfortunately, the Pivotal Tracker project is private so you may be unable to view the contents of the story.
The labels on this github issue will be updated when the story is started.
@ryanmoran , Do you have information about what we can add to the docs? I have been closing Issues that have had no activity, and I was about to close this one (2 years old) but I saw that you were watching it as recently as January 2023. Please let me know if there will be a PR for this or if it should be closed. If no action will be taken, we can close it.
No activity - closing.
Dear Sir,
The documentation doesent have an example of how to do routing between microservices with nginx buildpack.
How to do url based routing in nginx. We are giving the routes binded to an app in the upstream . However it is resolving to an ip and due to which go router is unable to forward the request to the appropriate IP
Request you to please create appropriate examples so that it benefits the users of the buildpack on how to route to other microservices directly using container to container networking or internal routes.
Also please create an example on how nginx can be used as a reverse proxy behind go router in Cloudfoundry for applications microservices with a static route bound to them
Also please crete examples for the below case
Abc.com/mservice1 -- maps to microservce 1
Abc.com/mcservice 2 - mapps to microservice 2
Nginx has more capabilities than go router and we wish to leverage that