Add PathBaseMiddleware to Aspire Dashboard

[mu88]

Hi 👋🏻

Disclaimer: Since my issue is more a feature request than an API change, I decided not to use one of the predefined templates, but I'm happy to provide any further information you need.

I'm running the Aspire Dashboard as a standalone app via Docker which works nicely 👌🏻 Since multiple Dockerized .NET apps are running on my host, I separated them by making use of the PathBaseMiddleware. This way, I can easily reroute them like this:

var builder = WebApplication.CreateBuilder(args);
var app = builder.Build();
app.UsePathBase("/myapp");

Applying this pattern to the Aspire Dashboard would probably mean adding the following code to DashboardWebApplication.cs:

if (!string.IsNullOrEmpty(builder.Configuration[DashboardConfigNames.PathBase]))
{
    app.UsePathBase(builder.Configuration[DashboardConfigNames.PathBase]); // maybe sanitize PathBase here
}

This way, I could easily reroute the Aspire Dashboard and make it accessible on https://myhost/aspire-dashboard instead of using a dedicated port (e.g. https://myhost:18888/). A corresponding docker-compose.yml could look like this:

services:
  aspire-dashboard:
    image: mcr.microsoft.com/dotnet/aspire-dashboard
    container_name: aspire-dashboard
    ports:
      - 4317:18889
      - 18888:18888
    environment:
      - Dashboard__PathBase=/aspire-dashboard

However, I didn't do a comprehensive and all-encompassing review of the implications and whether this might break certain features - but at least I want to trigger a discussion 🙂

[mitchdenny]

Do you have a reverse proxy in front?

[mu88]

yes, nginx

[mitchdenny]

OK thanks for the additional context. @kvenkatrajan not sure where this sits for you in terms of prioritization. It's the first request I've seen for this.

[kvenkatrajan]

Thanks @mu88 ..Interesting proposal.

@WardenGnaw / @tmeschter any impact to how this gets launched in codespaces?

CC: @karolz-ms , @drewnoakes

[fiotti]

Duplicate of #4159

[martin-gft]

Upvoting this as well!