-
Notifications
You must be signed in to change notification settings - Fork 543
New issue
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
Add PathBaseMiddleware to Aspire Dashboard #4528
Comments
Do you have a reverse proxy in front? |
yes, nginx |
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. |
Thanks @mu88 ..Interesting proposal. @WardenGnaw / @tmeschter any impact to how this gets launched in codespaces? CC: @karolz-ms , @drewnoakes |
Duplicate of #4159 |
Upvoting this as well! |
This will allow the aspire app to handle running behind a reverse proxy such as a k8s ingress on a subpath dotnet#4159 dotnet#4528 dotnet#5134
I created a PR for this #6963 |
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:Applying this pattern to the Aspire Dashboard would probably mean adding the following code to
DashboardWebApplication.cs
: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 correspondingdocker-compose.yml
could look like this: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 🙂
The text was updated successfully, but these errors were encountered: