Weekend project: A reusable deployment pipeline defined in C# that can take any aspire project and deploy it to a VM with ssh and docker. - Use of C# >>>> Shell scripts interleaved in YAML 🤮. - The pipeline code that runs over a model. This same code can... work for any aspire app without changes. It's a dynamic pipeline template. - It can run locally or in the CI - This was built on top of upcoming APIs in Aspire 9.4 (you can build your own pipeline and deploy anywhere too!) #dotnet #aspireshow more

when can we see "edge" ready :) @dwhiteindetroit

@ShawnCicoria what you and I talked about 😀

Oh wow. This covers the same use case as Kamal from 37 signals.

I did something like this pre-Aspire era to automate pipeline creation for new services. Previously my team was carefully following a multi page word document.

I’m curious, why are we skipping the packaging? This pipeline is not something we could use as we prepare versioned container images and helm chart for our service. Deployment is part of our CI pipeline, however it’s a step that runs multiple times with testing in between.

This is "interactive deployment" it does a few things: - Lets me test things out before I make it part of my pipeline. - It removes any dependency on external infrastructure for hobbyist scenarios This is not for enterprise deployment. At least I hope you're not deploying this way...

Really love the work you’re doing, keep up the good work!

Stopping existing containers => downtime...

Kinda off topic, but: is it possible to create an Azure Function with the new file scoped project type? And is there a way to connect to localDB from such project? AFAIK this needs a .csproj file.

It will be.