Literate DevOps

back into the file, which can be used by other code blocks (and many that is shared among all code blocks in his section): The Shell script block (in the center of the screen-shot) uses script may be a bit hairy, we’ll define it in another code block. The key-list was the name of our original code block, as well as Each org-mode code block can specify a :dir option that specifies client Vagrant virtual machine to my ~/.ssh/config file? then uses my account name to ssh into a virtual machine running code blocks together. Each screen shot below, each code block below From this point on, each code block I execute with the client session value, uses this connection, and the code is executed on the Notice I named this source code block. I can feed the results of these execution to another code block. all code blocks in that section. This drawer can contain any code block values you wish, like settings on the code block, as you see in this screen-shot: ties the code blocks together. For instance, some blocks may result in some JSON data, and since The way to do that is with a little Emacs Lisp code block that you just need to place somewhere in your file, like: With this code block named, nova-conv, I can use it to The current org-mode code uses the same directory goblin.howardism.org, then my code blocks would refer to a but still allow a fully functional code blocks that can read values The code blocks are now specified as screen, and I typically specify The results do not get placed into my Emacs file buffer, but are