Hi Akshay, it isn't clear from above writeup - is this open for self-hosting (I have an education usecase)? Couldn't find anything on this in the repo.
Thanks. marimo is cool, but spinning up N backends for scale would not be tenable cost wise.
Currently looks like there's this very cool full-frontend notebook tool: https://github.com/gzuidhof/starboard-notebook , which can be tied to a small backend to save/load python scripts from. This is working well for edu usecases potentially with support for both js and python.
This sounds like a good tool that would help ease the usage of adopting marimo for some of the tasks that people usually use colab for. It can be used for teaching and tutorials to share.
I just want to ask about Privacy Policy of the cloud version because I couldn't find it.
Thanks! Notebooks on molab are public (but undiscoverable, like public GitHub gists), and can be shared with links. This is described here: https://marimo.io/blog/announcing-molab.
Is there anything you are doing to prevent these notebooks from being indexed by Google/etc? Gists will show up in google search results if they've been linked from anywhere that google happens to find. The robots.txt just has 'Allow: /'.
I have no experience with Marimo so I guess I don't know the security model here.
More than that. marimo.app runs in the browser with WASM. That makes for a snappy experience but is limited in RAM and what kinds of packages can be run. This runs Python on a traditional backend, letting you use any package and any more resources.
Sorry! Did the notebook not connect to the runtime? Notebooks usually start quickly but there is variance, which we are working to tighten. If you have a notebook link/ID, we can look into it.
Marimo is the future of notebooks! This solves so many problems with collaboration using notebooks. Rooting for you guys!
Hi Akshay, it isn't clear from above writeup - is this open for self-hosting (I have an education usecase)? Couldn't find anything on this in the repo.
Hi! molab is not available for self-hosting. For self-hosting, you have a few options:
Use marimo open source. This can be self-hosted in the same way that Jupyter can. Repo: https://github.com/marimo-team/marimo
Use marimo's WebAssembly notebooks (exporting to WASM-powered HTML). For example, that's how Cloudflare is sharing marimo notebooks currently: https://notebooks.cloudflare.com/. Docs: https://docs.marimo.io/guides/exporting/#export-to-wasm-powe...
Use within JupyterHub: https://github.com/jyio/jupyter-marimo-proxy
Thanks. marimo is cool, but spinning up N backends for scale would not be tenable cost wise.
Currently looks like there's this very cool full-frontend notebook tool: https://github.com/gzuidhof/starboard-notebook , which can be tied to a small backend to save/load python scripts from. This is working well for edu usecases potentially with support for both js and python.
This sounds like a good tool that would help ease the usage of adopting marimo for some of the tasks that people usually use colab for. It can be used for teaching and tutorials to share.
I just want to ask about Privacy Policy of the cloud version because I couldn't find it.
Thanks! Notebooks on molab are public (but undiscoverable, like public GitHub gists), and can be shared with links. This is described here: https://marimo.io/blog/announcing-molab.
Is there anything you are doing to prevent these notebooks from being indexed by Google/etc? Gists will show up in google search results if they've been linked from anywhere that google happens to find. The robots.txt just has 'Allow: /'.
I have no experience with Marimo so I guess I don't know the security model here.
I just turned off /notebooks in robots.txt
Our thoughts are the same as gists- Molab is built to share your work and give you a place to tinker. Please don't put your api keys in there
> I just turned off /notebooks in robots.txt
That doesn't actually stop pages being indexed.
https://developers.google.com/search/docs/crawling-indexing/...
If your notebooks need keys, use mo.ui.text(kind=“password”), similar to the example from Hugging Face: https://molab.marimo.io/notebooks/nb_jpcTRt2jckij9iujuZ6NuZ
TY for marimo! A realy well thought out project solving lots of jupiter pain points.
I was hopeful for Wasm to make this work better but it just didn't. really cool to see this available - i was wondering what the next step was.
I think it would be better if there was a videotutorial to explain it.
We've got you covered: https://www.youtube.com/live/cYtWzIaGvb4?si=ZbhWEQBBv15yo8eq
I guess this is a persistent version of marimo.app ?
More than that. marimo.app runs in the browser with WASM. That makes for a snappy experience but is limited in RAM and what kinds of packages can be run. This runs Python on a traditional backend, letting you use any package and any more resources.
Everyone: don't push live on a Friday. marimo: ... hold my beer
Its completely failed several times in the course of an hour for me :'(
Sorry! Did the notebook not connect to the runtime? Notebooks usually start quickly but there is variance, which we are working to tighten. If you have a notebook link/ID, we can look into it.
Hey, if your name had an accent, workspace creation should have failed
Not sure how we missed that in testing. But it should be good to go now
Everyone knows prod doesn't break on the weekends