You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In a lot of typical Aspire use cases, the user deploys a reverse proxy. This YARP container could be used directly instead of adding manually a new project referencing YARP.
This container could also be used by developers wanting to try YARP directly, without needing to create and compile a new project.
The name of the container should be "reverse-proxy"
The text was updated successfully, but these errors were encountered:
IMHO, it's not a good idea to add a generic docker image for it. YARP is very basic and powerful reverse proxy skeleton. It's fully customizable and you can add so many features on top of it such as authentication, authorization, logging, tracing, metrics, direct forwarding, custom middlewares etc. Yes, you can set some of these features in configuration file, but you need to touch the code at some point.
YARP is a reverse proxy toolkit for building fast proxy servers in .NET using the infrastructure from ASP.NET and .NET. (https://github.com/microsoft/reverse-proxy/)
In a lot of typical Aspire use cases, the user deploys a reverse proxy. This YARP container could be used directly instead of adding manually a new project referencing YARP.
This container could also be used by developers wanting to try YARP directly, without needing to create and compile a new project.
The name of the container should be "reverse-proxy"
The text was updated successfully, but these errors were encountered: