11–20 of 47 posts
How is this better than actual Jupiter?
I have recently started using it at work, including extracting shell snippets into script files³ that are tested and reused in CI.
A frontend like this would be nice for bringing the interactivity to users of other editors!
--
I made a VSCode extension to do this but never published it. All it required was that md code snippets had a language annotation/label, and that you either had a default interpreter pre-installed or could configure an interpreter. I still have no clue why I did it NOR why I never published it.
It's like a specialised case of org-babel for the masses. Anyone with emacs can do this today, for free. The huge caveat is that it requires emacs. Where this tool shines, is that it's a superset of markdown, and thus not tied to any particular editor.
--
I like the idea of this conceptually but it feels that I could do all this with github actions. Is it the interactivity and ease of changing the script that is the selling point here?
How is this better than actual Jupiter?
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/
And you can run Jupyter notebooks from the CLI with Ploomber: https://github.com/ploomber/ploomber
How is this better than actual Jupiter?
There are actually many differences. We focus more on operational tasks, and allow cells to contain code from a number of programming languages in addition to python. In fact most folks are using Runme to make executing runbooks full of bash commands a better experience.
For those who don't know, Jupyter has a bash kernel: https://github.com/takluyver/bash_kernel And you can run Jupyter notebooks from the CLI with Ploomber: https://github.com/ploomber/ploomber
Earlier quoted context omitted.
There are actually many differences. We focus more on operational tasks, and allow cells to contain code from a number of programming languages in addition to python. In fact most folks are using Runme to make executing runbooks full of bash commands a better experience.
Ok, so from the front page I got the impression it was only bash. I'm hitting cloud APIs via python so Jupyter works for that, and I'm using the python to ssh into systems and run bash there. The two missing things from Jupyter are 1. ssh-ing to remote hosts and running shell scripts (we do it with a bunch of code) and 2. running cells concurrently. But python is a hard requirement.
We'd be interested to know how we can help Runme satisfy your use cases, join us on Discord! https://discord.gg/runme