Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Explain how to use aspire when deploying to a location that does not have built in tooling #1116

Closed
davidfowl opened this issue Jun 18, 2024 · 1 comment · Fixed by #1485
Closed

Explain how to use aspire when deploying to a location that does not have built in tooling #1116

davidfowl opened this issue Jun 18, 2024 · 1 comment · Fixed by #1485
Assignees
@IEvangelist
Labels
doc-enhancement Improve the current content [org][type][category] documentation Improvements or additions to documentation dotnet-aspire/prod in-pr okr-quality Content-health KR: Concerns article defects/freshness or build warnings. Pri1 High priority, do before Pri2 and Pri3 📌 seQUESTered Identifies that an issue has been imported into Quest.

Comments

@davidfowl
Copy link
Member

davidfowl commented Jun 18, 2024 •
edited by sequestor bot
Loading

There are LOTS of questions around how to deploy and run aspire outside of azure or outside of a Kubernetes based environment. Today aspire relies on deployment tools to extract the manifest from the apphost and translate it to some set of assets that can be applied to the deployment environment.

dotnet/aspire#1439 (comment)

In absence of this, we have no tooling story for users deploying to custom environments in the box. They can either build custom tooling or deploy like they were doing before.

This might be FAQ content.

Associated WorkItem - 297230
@dotnet-bot dotnet-bot added the ⌚ Not Triaged Not triaged label Jun 18, 2024
@IEvangelist
Copy link
Member

We do already have content on the manifest, that explains how tool builders might use it. And we do have various degrees of deployment content with the currently supported tooling. If this was a FAQ, I'd likely just link to those bits as we don't really have anything else to say about this yet, right?

@IEvangelist IEvangelist self-assigned this Aug 13, 2024
@IEvangelist IEvangelist added documentation Improvements or additions to documentation 🗺️ reQUEST Triggers an issue to be imported into Quest. Pri1 High priority, do before Pri2 and Pri3 doc-enhancement Improve the current content [org][type][category] dotnet-aspire/prod okr-quality Content-health KR: Concerns article defects/freshness or build warnings. labels Aug 13, 2024
@dotnet-bot dotnet-bot removed ⌚ Not Triaged Not triaged labels Aug 13, 2024
@IEvangelist IEvangelist mentioned this issue Aug 13, 2024
Merged
@sequestor sequestor bot added 📌 seQUESTered Identifies that an issue has been imported into Quest. and removed 🗺️ reQUEST Triggers an issue to be imported into Quest. labels Aug 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@IEvangelist IEvangelist

Labels
doc-enhancement Improve the current content [org][type][category] documentation Improvements or additions to documentation dotnet-aspire/prod in-pr okr-quality Content-health KR: Concerns article defects/freshness or build warnings. Pri1 High priority, do before Pri2 and Pri3 📌 seQUESTered Identifies that an issue has been imported into Quest.
Projects
No open projects
dotnet/docs August 2024 Sprint
Status: ✅ Done
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Address all open FAQ issues IEvangelist/docs-aspire
3 participants
@davidfowl @IEvangelist @dotnet-bot