tye VS draft

I think it's a good option or docker compose with your services only. Maybe check out project tye. Although it seems abandoned.

https://github.com/dotnet/tye for starting up many services/projects and tying them all together

Docker, and check out also Tye https://github.com/dotnet/tye

Or start all five with one command using https://github.com/dotnet/tye ! Same idea. Less typing.

You should use project tye. It was built for this use case. You can spin up all 5 with a single command. As if you ran dotnet watch run on each. You can add sql server or elastic search pretty easily. It works with webpack projects but is a bit janky. We use it to spin up 3 .net web apps, a react frontend, sql and elastic. All with a single command. https://github.com/dotnet/tye

The dotnet team at least does use it in a number of stuff. Tye's dashboard UI uses Blazor server, and if I recall some parts of MS docs uses Blazor WASM to evaluate C# code in the browser. dotnet live and https://themesof.net/ uses Blazor server as well.

+1 on dapr - also checkout Tye as well

https://github.com/dotnet/tye because if you have a project that includes a webpack build for the frontend, two separate .net core web apps, and you want it to log into elastic it can be a pain to get them all running. You can set up a tye config and start all those processes with a single command. Don't forget to start it in watch mode so your c# recompiles automatically too. Theoretically this can also be done in docker, but I've yet to figure out how to do that while getting debugging + watch working.

I am guessing they dropped it in favour of https://github.com/dotnet/tye

Acorn will take care of creating your Kubernetes manifest files but it expects that you have a Dockerfile ready to containerize your app. Instead of writing a Dockerfile from scratch, we'll use the Draft CLI to generate one for us. Draft is able to detect languages used within your project and generate the appropriate Docker manifest to containerize your app.

The development concept at level 2 is essentially the same as at level 1. The code is deployed via a pipeline to a Kubernetes cluster. However, at this stage, developers are using special CLI tools, such as Skaffold, Draft, or Tilt that detect the file changes by the developer and then automatically trigger the pipelines.

Does anyone know what happened to Microsofts Kubernetes project Draft? On GitHub it is marked as archived: https://github.com/Azure/draft