[admc]

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.

[lowbloodsugar]

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.

[admc]

I've just added the currently supported languages you can execute to runme.dev in the features section (Javascript, Typescript, Shell, Lua, Perl, Python and Ruby for now). Also, the Runme CLI (https://github.com/stateful/runme) also supports running cells in parallel with `runme run -all -p`.

We'd be interested to know how we can help Runme satisfy your use cases, join us on Discord! https://discord.gg/runme

[mst]

I wonder if you'd get some mileage from my https://p3rl.org/Object::Remote module (or at least stealing the ideas therein ;) - it effectively applies https://p3rl.org/App::FatPacker on-demand over the wire so the remote code can use any (pure perl) module you've got installed locally without needing to be able to write to the disk.

(at https://shadow.cat/ we use it to investigate things on new customers' platforms with only an ssh login and a perl core install as requirements, along with as an ad-hoc "I need to run this on lots of machines without being intrusive" tool)

[sourishkrout]

VS Code can attach to VMs via SSH and the notebooks will transparently run on the remote host. Python works out of the box as mentioned. I’m a co-creator of Runme btw.