David Arnold

A natural extension of this Idea would be a `mkRundeck` function that is like a manual & serialized version of a pipleline intertwined in a markdown document with apropriate emergency...

After my first half-way-through job implementation, I'm thinking that probably the best way to document a job is by just adding a `README.md` next to `main.nix`. - It will be...

I think I'll be working on this one next, since I want to set that standard & benchmark for our repo's evolution right from the start for myself & others.

This is going to be an absolute killer feature! :smile:

@kamadorueda You make me have an idea! Freeform, I guess is actually an advantage. Especially for things like runbooks, etc., which require some extensive context and explanation. However, we can...

Re: frontmatter Related #554

I'm predicting to hit this again somewhere around the next two weeks for more thorough design considerations :smile:

I figured that as a job runner, makes is actually perfectly suited for a command and control messaging pattern. I'm musing about a tiny wrapper-worker that just maps command messages...

Follow up question: Can we explore standardizing the task interface around some sort of "message format" with the end goal of saddling `makes` jobs onto an orchestrator (such as airflow/zeebe/you-name-it)?

> 100% of the parallelization happens within Nix itself.  I'm thinking of a use case where a baked task can shell out to a (slow) remote APIs and make use...