Simplify deployment overview #35
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Learn Build status updates of commit 662dc4f: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
IEvangelist
requested changes
Nov 14, 2023
docs/deployment/overview.md
Outdated
| # .NET Aspire deployments | ||
|
|
||
| .NET Aspire applications are cloud agnostic and should be deployable to any cloud environment that supports .NET and containers. For example, the steps in [Deploy a .NET Aspire app to Azure Container Apps using the Azure CLI](azure/aca-deployment.md) can be adapted to other cloud environments, or local hosting. However, deploying manually requires a number of steps which are exhaustive and error prone. We expect most customers to want to deploy Aspire apps using some form of CI/CD, using cloud specific tooling. | ||
| Once you're happy with your .NET Aspire application, it's time to deploy it - either to a cloud environment or to local hosting. .NET Aspire isn't tied to any particular cloud and the steps in, for example, [Deploy a .NET Aspire app to Azure Container Apps using the Azure CLI](azure/aca-deployment.md), are adaptable to other environments. |
There was a problem hiding this comment.
You're the expert, but won't it-either, hyphenate rather than emdash?
Why is there a stray ~?
Aren't "regardless of the destination" and "cloud-agnostic" redundant?
amcasey
commented
Nov 14, 2023
docs/deployment/overview.md
Outdated
| # .NET Aspire deployments | ||
|
|
||
| .NET Aspire applications are cloud agnostic and should be deployable to any cloud environment that supports .NET and containers. For example, the steps in [Deploy a .NET Aspire app to Azure Container Apps using the Azure CLI](azure/aca-deployment.md) can be adapted to other cloud environments, or local hosting. However, deploying manually requires a number of steps which are exhaustive and error prone. We expect most customers to want to deploy Aspire apps using some form of CI/CD, using cloud specific tooling. | ||
| Once you're happy with your .NET Aspire application, it's time to deploy it - either to a cloud environment or to local hosting. .NET Aspire isn't tied to any particular cloud and the steps in, for example, [Deploy a .NET Aspire app to Azure Container Apps using the Azure CLI](azure/aca-deployment.md), are adaptable to other environments. |
There was a problem hiding this comment.
You're the expert, but won't it-either, hyphenate rather than emdash?
Why is there a stray ~?
Aren't "regardless of the destination" and "cloud-agnostic" redundant?
IEvangelist
reviewed
Nov 14, 2023
IEvangelist
approved these changes
Nov 14, 2023
|
Learn Build status updates of commit 8d38d34: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.