mdsh

Can you compare to https://github.com/bashup/mdsh ?

Telling computers what to do and how to do it is an art, a craft, a practice, a discipline, a medium, a profession, and a science (and probably a few more categories besides). It is just isn't (usually) all of those things at once. Most of the difficulties we have in discussions about the subject have to do with category errors. Literate Programming has stylistic, technical, toolchain, and disciplinary aspects, and Knuth's exemplar demonstrated these. It was then critiqued on pragmatic grounds. I'm not sure if this counts as a bait and switch, rope a dope, or strawman. I mean, if I was participating in a computer programming class and given the same problem as an assignment, I would write a program to satisfy the requirements. If then told that I should have written a few lines of shell script instead and given a poor grade, I would be li

I've seen a few posts here recently on literate programming; I really hope it takes hold as a trend. A couple of months ago I released a "literate devops" tool: https://github.com/robsheldon/golem/ It extends https://github.com/bashup/mdsh so that you can execute shell code, embedded in markdown, on remote servers. I hope someday that documented server management becomes the standard.

Examples of brittle but approachable approaches we’ve used: - Literate bash: https://github.com/bashup/mdsh - Ansible: https://github.com/bmacauley/ansible-playbook-mac-dev/blob/m... - Kubernetes: https://abhishek-tiwari.com/local-development-environment-fo... Example of solid and shareable at scale approach, takes a bit of rocket surgery: -Nix: https://dzone.com/articles/isolated-development-environment-... To be clear, we had a Nix committer to help work through kinks. But once all of your team members, local and remote, have lockstep dev environments versioned with the code commits, several other classes of hair pulling go away.