Markdown viewer for Bash

Runbooks, setup steps and on-call notes with shell commands that are easy to follow.

Paste a markdown runbook or setup guide with Bash commands, read it rendered with the shell code highlighted, and share it with a link that opens without signing in.

Shell commands in markdown are usually instructions for another person. An on-call runbook says which command drains a node and which one checks it is empty. A setup guide lists the steps a new hire runs on day one. A release checklist strings together the tags, builds and uploads in the right order. When someone follows these under pressure, they need to see clearly which lines are commands, which are comments, and where one step ends.

The rendered page gives each step a heading or a numbered item, and inside the Bash blocks variables, strings, built-ins and comments are colored, which helps catch an unquoted variable or a pipe that was meant to be two commands. A table of contents is generated once the runbook has three or more headings, so a long procedure stays navigable.

Nothing in the document is executed by sharemd.net; the commands only run when a reader copies them into their own terminal, so review them before you share. The read-only link is reachable only by people who have it and is not indexed, but anyone with it can read the content, so leave tokens and passwords out. The page expires 15 days after it is created.

How to view Bash in markdown

  1. Paste your markdown into the editor above, or edit the example.
  2. Wrap Bash code in a fenced block that starts with ```bash.
  3. The preview shows the rendered document with the code highlighted (side by side on desktop; switch to Preview on a phone).
  4. Select Share to get a read-only link that anyone can open without an account.

Frequently asked questions

Do sh and shell tags get highlighted?

Yes. ```bash, ```sh and ```shell all use the Bash grammar. ```zsh and ```console are not mapped and render as plain monospaced text.

Can readers run the commands from the page?

No. The page only displays them. A reader has to copy a command into their own terminal to run it.

Is it safe to include API keys in a runbook?

Leave them out. A shared document is not indexed by search engines, but anyone who has the link can read it, and there is no password protection.