indigo fulcrum
@neat plover showcases the latest integration of Runme Notebooks with Dagger Shell—bringing a seamless, interactive way to define, debug, and execute pipelines right inside VS Code-style environments. Learn how Dagger Shell enhances workflow efficiency, enables modular execution, and makes debugging a breeze. https://youtu.be/VGQhYHaIBwE
🔗 Try it out: https://github.com/stateful/runme
cold nebula
Nice, loved the demo @neat plover, thanks!
neat plover
Thanks @cold nebula!
jolly schooner
interesting, wondering if it solves this issue here? #general message
jolly schooner
possibly integrating with https://marimo.io/ would also be nice
neat plover
Hi @jolly schooner, I can't speak for Marimo but I'm one of the creators of Runme and have built the Dagger Shell integration
you could drop these Runme for Dagger notebooks into a shared repo or run an instance of https://github.com/coder/code-server to host them internally
What's neat about Dagger is that even with a shared repo it's simple to leverage your local compute/mem to run tasks/workflows since the container abstraction decouples it from the host
jolly schooner
nice! Runme is really cool! I've had a few issues though running it on the CLI (added issues on Github), and wondering if there's a way to disable "run all" on some files by adding some header? I'd like to document some business process, but wouldn't want someone to mistakenly run everything etc
also it's not very clear when I'm editing a cell if everything's being re-run again etc
it's fine for idempotent code, or stuff that's not modifying the state of the db, but I might have some code that I don't want to run multiple times, is new code run only when I'm pressing the "play" button ?
neat plover
in order, sorry about this issue https://github.com/runmedev/runme/issues/770, it's a problem with code-server which I have reported a while ago. i'll ping them again and update the issue.
cells only run when you click the respective ▶️ button
jolly schooner
okay thanks!
neat plover
it's all shell expect for Dagger, that's Dagger Shell which is special
jolly schooner
really like your project, I also add a vision of building something similar so now I don't need to haha
if I can do a small suggestion though
I'd really like a nice and clean UX (on the server) that looks something like this https://app.duckbook.ai/
neat plover
but nonetheless, cells only run upon explicit "run"
jolly schooner
shouldn't be too complex to build on top of what you've already built
neat plover
i see, kinda like a "notion-kind" of experience
jolly schooner
but I find it much smoother than the "VSCode plugin"
jolly schooner
i see, kinda like a "notion-kind" of experience
yeah, really just the UX
behind it would be the same markdown
and just some "visualization widgets"
that are rendered
it's just a "nicer renderer" than the VSCode plugin, and which would be directly hostable on the web on our intranet or whatever
neat plover
you know it! working on something like that but it's in a prototype stage
jolly schooner
very nice!
neat plover
i'll keep you mind once I need beta testers 😄
jolly schooner
ah, how do I do this?
neat plover
run code-server vanilla
neat plover
and then in the web UI in the extension tab
you can explicitly ignore the signature check
jolly schooner
okay
thanks!
BTW it would be so nice to have it easy to install through "mise"
I use mise for all my tooling
and it's close to being possible
you can do mise use go
then `mise use "go:github.com/...yourRepo"
but for some reason there's a bug when I do that
neat plover
feel free to open an Github issue for mise support
i suspect it's fixable if it's based on git
jolly schooner
yes, I think I mentionned it in the issue, but I'll do a proper one sure!
it's really nice so that all the developpers in the team have the exact same versioned tools
a "mini-nix"
but much easier
neat plover
merci! i'll be sure to triage/update those issue
jolly schooner
BTW what's the point of using the runme cli rather than the VSCode extension?
is the runme cli needed for the VSCode extension to work, or they are unrelated?
neat plover
Notebook and CLI share a common kernel
you can use the CLI to run your notebooks headless
like in CI/CD or when you use it like a task runner
jolly schooner
ah thanks! very clear
hmmm BTW trying to run a few commands on the notebook, but when I'm trying to git clone a private repo it doesn't find the key... I guess I might have to redirect the shell or something?
neat plover
the idea of the kernel architecture is to allow multi-modality (terminal, browser, notebook, editor etc) for different use cases
do you usually have a ssh-agent running?
jolly schooner
quick question: (but I guess I should read the doc), is the $CWD "kept" between all the cells, or if I "cd" in a cell, I need to do it again in the next?
neat plover
one sec
you can send cwd in the frontmatter of the document
or overwrite it per cell in the Configure menu
to be clear, they cwd is not kept between cells. they run in isolation. however, we do retain changes to the ENV.
neat plover
feel free to ping me any time, here or on Runme's discord
jolly schooner
would there be a way to add an option to the VSCode plugin so that it does the Markdown render by default only if the extension is file.x.md (eg x for executable) or file.runme.md ?
so that I can still browser "normally" my other non-runme markdown files?
neat plover
you can use *.runme or *.run as an extension @jolly schooner
and then do this for *.md: https://docs.runme.dev/installation/vsx#change-your-default-markdown-viewer
It's a user controlled thing where the extension won't let Runme decide