Skip to main content

Runme by Example

Discover the various ways you can use Runme to run your code straight from your Markdown file. Explore our example page to learn more exciting ways you can use Runme. These examples showcase improved ways you can use Runme, such as in hardening your Ubuntu server, within your dev container, etc. In this section, you will find a variety of features and examples to help you get the most out of Runme.

1. Advanced Usage of Piping and Variables

Runme was configured in a default mode to prevent variables in one cell from being accessed directly in another cell. However, you can let go of this default mode by using Piping which is declared using $__, to pass a variable declared in a previous execution to another cell in the same file.

Runme swiftly allows for complex piping and usage of variables across cells. Here is an example using Git:

  • List Git Branches Matching a Pattern:
git branch | grep "feature-"
  • Process the Output in a Subsequent Cell:
echo "$__" | while read line
if [ ! -z "$line" ]; then echo "Feature branch: ${line}"; fi

2. Working with Stdin, Stdout, and Stderr

As a system administrator or developer, using standard streams for scripting, automation, error handling, and managing system resources is one common task in your day-to-day life.

In this section, we have crafted examples to demonstrate various ways to work with stdin, stdout, and stderr, in Runme.

  • Reading from stdin and writing to stdout:
$ cat
Enter your text here.

In this example, cat is invoked without any arguments, so it waits for input from stdin. After entering text and pressing ^D (Ctrl+D), it writes the input to stdout.

  • Redirecting stdin and stdout:
$ cat < input.txt > output.txt

Here, cat reads from input.txt (redirected stdin) and writes to output.txt (redirected stdout).

  • Appending to an Existing File:
$ echo "New content." >> existing_file.txt

This appends the text "New content." to the file existing_file.txt.

  • Redirecting stderr:
$ ls non_existent_dir 2> error_log.txt

If ls encounters an error (like trying to list a non-existent directory), the error message will be redirected to error_log.txt.

  • Redirecting stderr to stdout:
$ ls non_existent_dir 2>&1

This redirects both stderr and stdout to the same destination, which is typically the terminal.

  • Piping Output:
$ ls | grep ".txt"

This pipes the output of ls (which lists files and directories) to grep, which filters lines containing ".txt".

  • Redirecting stdout and stderr to Different Files:
$ myprogram > output.log 2> error.log

This runs myprogram, directing stdout to output.log and stderr to error.log, allowing for separate logging of standard output and error messages.

You have just seen some improved ways you can use Runme in your documentation, but that’s not all!

If you encounter any challenges with these practices, please don't hesitate to reach out to us. We would be glad to assist you.