Looking for a way to statically host several notebooks, without having an 18M directory per notebook.

[ekiim]

Hope the title gives a good idea of what I am trying to do.

Basically I have a project directory with my notebooks in a directory called src (for example example.py), and I would like to have a Makefile (or just build scripts) that "publish" the notebooks in build/example.

This is perfectly doable by having a build rule as (I could drive the rule to be different if I need):

marimo export html-wasm  -o build/example --mode run --show-code src/example.py

The problem is that I measured (du -hs build/example) the output and the directory is 18M. (This was for a notebook which just prints a hello world) The issue is that whenever a "user" navigates from one notebook to another it would re-download everything, and this would make the experience not great.

If I want to publish on my own site multiple notebooks, I would end up with 18M per notebook, which I would assume they'll have redundancy. (meaning that I would have basically identical files, if not identical, on multiple directories),

Is there a solution to have like the "basic boiler plate" in a separated directory and have it to be shared across multiple notebooks?

A solution like this, would allow the "user" to just have the first big "network hit" (because of the download), the first time they load a page for a notebook, and the second time, hopefully it would be cached by the browser making it slightly better.

My purpose is to share notebooks in my own static page.

If anyone has already encountered and solved this issue, please let me know.

[akshayka]

Have you seen the gh pages template? I believe it does what you want, sharing a single assets folder for multiple notebooks.

https://github.com/marimo-team/marimo-gh-pages-template

[ekiim]

Ok, so basically the solution is to build all the notebooks (depending on their build parameters) on top of the same directory such that

marimo export html-wasm  -o build/app --mode run --show-code src/example-A.py
marimo export html-wasm  -o build/app --mode run --show-code src/example-B.py

And in principle they should not have conflicts with their other dependencies, or that is what I've understood by inspecting the build script.

The index page was an really nice extra ;)

Thanks.