tye VS draft

System.CommandLine is the official .NET library that provides common functionality for command-line applications. This includes features like argument parsing, automatic help text generation, tab autocomplete, suggestions, corrections, sub-commands, user cancellation, and much more. Many official .NET tools are built on top of System.CommandLine, including the .NET CLI, Kiota, Tye, numerous Azure tools, and other .NET additional tools.

I though tye was a typo but it is an actual project: https://github.com/dotnet/tye

I would like to build modules, either in a modular monolith style, or in a microservice style using DAPR and/or Tye.

GitHub: https://github.com/dotnet/tye

If you like working with docker compose, you might want to take a look at https://github.com/dotnet/tye

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

Thoughts on scaffold vs Tye ?

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

Draft exists to help folks get up and running on Kubernetes more easily.

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.

Draft is an open-source project that streamlines Kubernetes development by taking a non-containerized application and generating the Dockerfiles, Kubernetes manifests, Helm charts, Kustomize configurations, and other artifacts associated with a containerized application. Draft can also create a GitHub Action workflow file to quickly build and deploy applications onto any Kubernetes cluster.

Azure/draft where it's an archived repository

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

Many of the PaaS open source implementations whether built on top of k8s or otherwise turning up dead or getting lower and lower traction. Examples would be flynn.io, for example or draft (https://github.com/Azure/draft) seems also sort of dead. What gives? What's happening? Is there no place for PaaS anymore because there are too many already? Or k8s deployment and operation is that simplified to the point that with Helm, Tekton and Brigade etc - there's a general convergence on a DIY K8s and away from PaaS layers even if they're built atop K8s?