News for hackers. Stuff that matters.
Re:Runme – Interactive Runbooks Built with Markdown by theossuary on Thursday August 24, 2023 @06:47PM (#37255546)
I wouldn't squirrel my documentation away in an ipynb file. So even though I'd like to use notebooks as runbooks, Jupyter just isn't the right solution for that. This could be a great tool for when you want to augment markdown documentation with runnable snippets. I really like this idea, it gives off literate programming[0] vibes.

[0]: http://literateprogramming.com/

Re:Runme – Interactive Runbooks Built with Markdown by joncp on Thursday August 24, 2023 @06:56PM (#37255617)
Another is that it looks like runme is written in Go instead of python. It's a single executable I can drop onto any new machine instead of futzing around getting a particular python version installed before doing any work.
Re:Runme – Interactive Runbooks Built with Markdown by admc on Thursday August 24, 2023 @08:26PM (#37256307)
I'm on the Runme team, and one of the goals of the primary goals of runme is to use a shared markdown parsing engine so that the behavior in the CLI, the VS Code notebook and in a Github action is consistent.
Re:Runme – Interactive Runbooks Built with Markdown by admc on Thursday August 24, 2023 @08:47PM (#37256474)
You nailed it, thanks for calling that connection out. We were very much inspired by literate programming.
Re:Runme – Interactive Runbooks Built with Markdown by enriquto on Friday August 25, 2023 @05:45AM (#37259830)
> I wouldn't squirrel my documentation away in an ipynb file.

This! ipynb files are a nightmare to deal with. Fortunately, you can use jupyter without ever seeing a .ipynb file, by storing your notebooks in a different format (e.g. as programs or as markdown files). Bonus points: you'll hear fewer complains from your local graybeards if they can edit and run notebooks from their favorite text editor.