JupyterGIS breaks through to the next level

Re:JupyterGIS breaks through to the next level by skissane on Friday October 24, 2025 @05:55AM (#45692829)

> How does that work? I can apparently make changes to the files, and even save them, but then my changes are gone when I reload it. Where were the changes saved? This is exactly what I'm wary of when using Jupyter...

The GP linked to JupyterLite, which is browser-based Jupyter based on WebAssembly...

Then there is JupyterLab which runs on your own machine, or on a server somewhere (e.g. a K8S pod)...

And then there are options like JupyterHub and Kubeflow which start K8S pods for you dynamically to run JupyterLab in...

So "where is my data stored" all depends on how Jupyter is deployed... at the moment, when I use Jupyter, I'm mainly using it running inside a Docker container which in turn runs inside a K8S pod (weird way of deploying it, but I have my reasons)... and then the notebooks are stored in a volume (PVC) attached to the K8S pod (statefulset actually), but that's just temporary storage while I work on them, anything I want to keep permanently is put in Git and pushed to our corporate Git host... and then our actual datasets are mostly on S3 (or something else which speaks the S3 protocol)

[ Parent | on HN ]

Re:JupyterGIS breaks through to the next level by tasuki on Friday October 24, 2025 @02:59PM (#45697965)

I don't know! They said "collaborative" and they provided a link. I tried making some changes to test the collaboration and clicked the "save" button. It changed the "last changed" to "now" and upon reload my changes were gone.

It lied to me: my changes weren't saved! If I can't save a thing, I want to be explicitly told so!

[ Parent | on HN ]

Re:JupyterGIS breaks through to the next level by skissane on Friday October 24, 2025 @11:31PM (#45701173)

I’m pretty sure it saves it using browser storage APIs… so rather than it lying to you, it could be your browser (or some extension even) lying to it

[ Parent | on HN ]