rustshop VS js-yaml

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.

Parse the source string. We're using js-yaml for this.

Character limit is not enforced, and in practice, popular yaml implementations such as yaml/js-yaml don't impose any fixed limit.

The main reason behind this release is native YAML support in front-matter thanks to js-yaml library. This means you have to assign the tags key as yaml arrays otherwise, Action will throw an error or ignore the assigned tags.

js-yaml