Notebooks are loaded from another instance if multiple instances are hosted on the same domain

Description

Hosting multiple JupyterLite instances on the same domain (e.g. GitHub pages) leads to a weird behavior for equally named files. Completely different .ipynb files from instance A will be loaded when you afterwards visit instance B.

Reproduce

1. Go to project https://leukipp.github.io/jupyterlite/lab/, forked from the demo repository.
2. Open python.ipynb, make some changes and save.
3. Go to another project https://leukipp.github.io/xmastree/lab/, which also contains a file named python.ipynb.
4. Open python.ipynb, the content from the previous visited notebook is loaded.

Expected behavior

Notebook states should be loaded correctly, regardless of the previously visited instances.

Context

• JupyterLite version: v0.1.0a18

Possible Solutions

• Use different indexedDB database names per JupyterLite root path (currently always JupyterLite Storage is used)
• Use relative filepaths inside indexedDB database (e.g. /jupyterlite/lab/… or /xmastree/lab/…)

[bollwyvl]

generate an unique id

mmm… smells like magic.

If a sequential id generator

At some point, we’d probably just add git or fossil provider for #315 rather than re-inventing it poorly.

I’ll go forward with the simplest addition of a localStorageName entry for jupyter-lite.json. This would give a site deployer the ability to override it if they don’t want the default behavior, but not change the existing behavior too much.

[bollwyvl]

shipped and documented in 0.1.0a20, please re-open (or raise a new issue) if new issues related to multiple sites-per-host persist.