I think we can consider providing several deployment methods in the first stage.

[bit365]

Regardless of whether you generate a deployment manifest or use any method, you want to deploy the developed aspire project to the target server. Currently, there is no more convenient deployment. This is a problem that needs to be solved.

1. Use visual studio to right-click on the Aspire.AppHost project to publish, or dotnet publish command to publish. The non-container part deploys the folder directly. The container part needs to generate a docker image and then deploy it to the target server. You can consider generating docker-compose.yml file and then deploy using docker-compose, this should all happen automatically.

2. Use the kubectl command to deploy the aspire project to the target server. This should be completed automatically.

Aspire's resources come in different forms, generally including containers, executable files, web project types, etc. The deployment methods of these resources are also different, and you need to consider how to deploy them better.

The deployment list may need to be abstracted so that it can be better managed. There should be a tool or command that can automatically deploy the aspire project to the target server based on the deployment list. This would be perfect.

[davidfowl]

Use visual studio to right-click on the Aspire.AppHost project to publish

This is being worked on but for deploying to Azure container apps.

Use the kubectl command to deploy the aspire project to the target server. This should be completed automatically.

This is being provided by aspirate

The container part needs to generate a docker image and then deploy it to the target server. You can consider generating docker-compose.yml file and then deploy using docker-compose.

Aspirate can also generate a docker compose file. So you can use the same tool mentioned above in that situation.

Each deployment target needs to translate the manifest to the target environment's resources. There's no one tool that will be built to support all environments. We plan to support azure container apps via AZD for v1 and aspirate will provider Kubernetes support. We're working with Amazon to provide AWS support as well.

Beyond that there will be no other supported environments for v1.

[bit365]

Thanks！

[davidfowl]

Use visual studio to right-click on the Aspire.AppHost project to publish, or dotnet publish command to publish. The non-container part deploys the folder directly.

What would you do with this?