Proxy is supplied as a pre-built exe with core functionality available via configuration

[samsp-msft]

The original issue #247 got hijacked as a request for docker, so forking this as an issue for creating an exe.

We've proposed shipping YARP in three formats:

• A library - https://www.nuget.org/packages/Microsoft.ReverseProxy/
• A template - Proxy is supplied as a project template for dotnet new #77
• A pre-built application exe (this issue)

The pre-built app should:

• Read from a config file
• Cover basic scenarios
• Support a variety of platforms

Scenarios

• Config based routes, clusters, & backends

• Remote route config? E.g. load from a database, service fabric, k8?

• Dashboards? Proxy Status dashboard (product feature) #123

• Health checks for the proxy itself.

• Static files? Proxy can deliver static files directly #187

• Auth?

• Multi-instance?

  • Data protection (Session Affinity)

• Single-file exe with linking: Enable IL Linker and Single-File in the Proxy #7

• Config UI? Configuration UI for routes (web) #184

Config

The library already supports loading routes from a config file. However, an app will need to expose additional config for the scenarios described above.

Platforms

• Windows, Mac, Linux
• Builds for both runtime dependent and standalone (servicing?)

Acquisition

• Microsoft download center?

[Tratcher]

Brainstorming:
dotnet yarp global tool that runs the single file exe using appsettings.json in the local directory.

Compare to dotnet serve.