We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Orchestrator is now itself the load balancer and reverse proxy, rather than using NGINX in front of .NET.
The text was updated successfully, but these errors were encountered:
Possibly #12
This needs revisiting
Sorry, something went wrong.
Closing this as we have the basics for a YARP-based Orchestrator implementation. Tickets can be tracked on Orchestrator board or orchestrator .
Regarding the 3 points raised in the initial comment:
donaldgray
No branches or pull requests
Orchestrator is now itself the load balancer and reverse proxy, rather than using NGINX in front of .NET.
The text was updated successfully, but these errors were encountered: