rustshop VS dho

I was hoping to have https://github.com/rustshop/rustshop be like that, but I've got a Rust dayjob since then, and I have less time for Rust side projects now.

Many thanks to u/dpc_pw, whose notes on GitHub were my starting point for the flake definition. (I also just realized I unwittingly gave my article an almost-identical title by the time I was done refining it, so I’m more indebted to them than I thought.)

Since docker images are mentioned, I'd like to point out that using musl-linked images is often counterproductive, as docker layers with standard library can be shared between different projects and build versions. https://github.com/rustshop/rustshop/discussions/9

and here is the project in this area that I'm working on

rustshop is an attempt at building a template for developers to help them start their own cloud-based system, without much Ops experience.

not to argue, but why do you need a "general purpose lang" for this? turing-completeness is a liability in this case IMO (i'm genuinely curious) I've actually experimented generating k8s yamls from a nice DSL described in dhall a while ago just never completed: https://github.com/ababkin/dho Done this way, i don't believe this is true: "will let you create non-existing properties in wrong places and discover it only much later down the line" Don't know what you mean by "doesn't have the understanding of underlying data"