5 ms·

How is this better than actual Jupiter?

theossuary 3y ago
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/ http://literateprogramming.com/
- joncp 3y ago
  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.
  - admc 3y ago
    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 there is consistent behavior between CLI/GH Action and the VS Code Notebook.
- admc 3y ago
  You nailed it, thanks for calling that connection out. We were very much inspired by literate programming.
- enriquto 3y ago
  > 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.
admc 3y ago
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 3y ago
  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 3y ago
    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 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 https://discord.gg/runme
    - mst 3y ago
      I wonder if you'd get some mileage from my https://p3rl.org/Object::Remote https://p3rl.org/Object::Remote module (or at least stealing the ideas therein ;) - it effectively applies https://p3rl.org/App::FatPacker 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/ 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 3y ago

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/ http://literateprogramming.com/

joncp 3y ago
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.
- admc 3y ago
  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 there is consistent behavior between CLI/GH Action and the VS Code Notebook.
admc 3y ago
You nailed it, thanks for calling that connection out. We were very much inspired by literate programming.
enriquto 3y ago
> 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.

admc 3y ago

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 3y ago
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 3y ago
  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 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 https://discord.gg/runme
  - mst 3y ago
    I wonder if you'd get some mileage from my https://p3rl.org/Object::Remote https://p3rl.org/Object::Remote module (or at least stealing the ideas therein ;) - it effectively applies https://p3rl.org/App::FatPacker 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/ 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 3y ago