-
Notifications
You must be signed in to change notification settings - Fork 496
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
Allow Dashboard to be used standalone #847
Comments
Duplicate of #846 |
I don't think this is duplicate of that one. Adding Aspire to an existing project (as in no extra workload process) is different that running Aspire as a standalone project. From what I can gather, there is more appetite inside Microsoft to do a standalone instance than make it work as an add on to an existing app. |
Agreed @martinjt, re-opening this to track the standalone scenario, e.g. as a dotnet tool and/or container image. |
Confused this and #846 |
I'm closing this in favor of #1003 |
The Dashboard is great, and something that is much needed for local development, that's beyond the Cloud Native part.
I think it would be great if the Dashboard were to be available as a docker image that people could spin up and use. A few things that would make that more useful.
Making the TelemetryRepository an interface would allow for the container to have something like a sqlite db under the hood so it can live beyond restarts, but obviously wouldn't be great performance wise, so it could be used in production.
If it's something that's of interest, I could definitely PR some of it in.
The text was updated successfully, but these errors were encountered: