Add a new deployment option for .Net Aspire #2024
Replies: 3 comments 5 replies
-
|
I tried it using aspirate, which can create a docker-compose file The only thing that I get stuck on is that locally I run 'aspirate build' to push the images to Docker Desktop. This does not happen automatically in coolify as the generated docker compose is aimed at pushed images, instead of referencing Docker files. I think Aspire is really cool, it works well on Azure, but none of this (docker stuff) is really supported and I ended up doing a lot of things manually which defeats the purpose. This could be adapted though https://github.com/prom3theu5/aspirational-manifests to generate docker compose files suitable to coolify :) |
Beta Was this translation helpful? Give feedback.
-
|
I did take a look at your source code as I tried basically the same, create a solution with .NET Aspire and somehow generate a docker-file.yml, then referencing it in a project in Coolify but had no look, I have problems with ports and stuff. Specially when using containers like Keycloak, or even normal APIs. Did you manage to make it work? I did try with your repo (https://github.com/coen22/AspireDockerComposeSample.git) and I get that error too, maybe I'm not doing it correctly? I think supporting this in Coolify would be a gamechanger for people that skips cloud.
|
Beta Was this translation helpful? Give feedback.
-
|
Aspirate did make some changes to support compose build from dokerfile. It might be possible now? With aspire 9 they also ship an image for the aspire dashboard. When you deploy to azure with azd cli it also gives you that dashboard. |
Beta Was this translation helpful? Give feedback.
-
|
So, the thing is, it does deploy. Or it used to for me, at least. But the big problem that I still have is the automatic routing. How to make sure that the frontend knows where the backend is. |
Beta Was this translation helpful? Give feedback.
-
|
When using a blazor project with API and frontend. It puts those on the same port, so then it does work to deploy using a Dockerfile by pointing coolify to a Github repo. It automatically deploys everything. But what I did with that test is, I used an Sqlite database, which doesn't require a separate connection. Though I assume it could find a postgres database on its localhost when configured through aspire. I've not deployed any aspire project to Azure itself, but that could explain something about how Microsoft configures those routes without having it be made explicit in the code (i.e. you could always define the api.example.com in the main aspire project). |
Beta Was this translation helpful? Give feedback.
-
|
Deploying multiple apps like API + Blazor or even API + NextJS should be possible via aspire - you can do it with a docker compose so not sure why it would be a problem in aspire. |
Beta Was this translation helpful? Give feedback.
-
|
Some other options for supporting native .NET deployments here might be:
|
Beta Was this translation helpful? Give feedback.
-
|
This would be huge for .NET devs. Big +1 |
Beta Was this translation helpful? Give feedback.
-
.Net Aspire is a new development model Microsoft is pushing for .Net 8+ (which can run on Linux) that allows the project to manage the orchestration of services automatically. Read more
Another project called "Aspirate" is available that can take a .Net Aspire project and generate docker compose or kubernettes manifests from it. Read more
Together these could be used in a new build pack to build/publish .net Aspire application stacks along with spinning up containers for all required services. Aspire takes care of passing the connection strings and other details through to the various applications.
Supporting this would allow Coolify to get ahead of the game on containerised hosting and orchestration.
Beta Was this translation helpful? Give feedback.
All reactions