golem VS nasty-files

This is the method I ended up using for golem (https://github.com/robsheldon/golem), a tool I wrote for executing server documentation on remotes. Shell quoting was by far the hardest part to get right, and the base64 pipe was the only solution that correctly handled all forms of quoting embedded in the scripts.

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.

I use this pattern a lot along with a tool I built for doing server deployments and administration using plain old shell scripts and ssh (golem: https://github.com/robsheldon/golem/).

There are two caveats:

First, if there's any chance at all that the heredoc may contain a $, or a `, or possibly some other shell-magical characters, then you have to use a single-quoted heredoc:

  cat <<'EOF'...

I made a whole collection: https://github.com/benibela/nasty-files

I have a collection of non-utf8 and other problematic files:

https://github.com/benibela/nasty-files

You probably cannot clone the repo on Windows. It works well on Linux. But in KDE you could not delete it afterwards