|
|
|
|
|
by e12e
1935 days ago
|
|
I like the idea, but I think I'd prefer to go more towards mdsh - I already write up markdown documents for various tasks - I would prefer extracting and running code directly from file (eg: a local checkout of a gitlab wiki project, or from a docs-folder in a checkout of a regular project). Maybe I can bend mdsh to my needs with a bit of inspiration from your project. Currently there's expected to be a bit of copy paste from the wiki/rendered markdown - but that only scales so far. (I generally do drop helper scripts in a project /bin folder, and document the use of those via markdown - but having a sensible way to execute code blocks would maybe help). Ed: Or perhaps I'm better off just using https://zyedidia.github.io/literate/index.html directly. |
|
I used that trick for a while, but it required the `--compile` option for mdsh, and re-compiling each script every time was silly. Also, I wanted shellcheck to look at the output each time to make sure something wasn't horribly broken before running some markdown on a server. (Other than the part where I'm running markdown on a remote server.)
So, I started caching the compiled files. Then I wanted a couple of convenience functions added to them. Then golem sort of happened.
It pretty much just takes mdsh and makes it safer and nicer to run on remotes.