How to save browser/server state? Docker/Containers?

stevenkan

Ars Legatus Legionis
15,662
[mods: please move to wherever you think this oughta live, as it doesn't appear to belong in any existing forum]

I like to make 360º panoramas, and it's nice if I can assemble them into virtual tours with hotspots.

The most convenient tool I've found thus for for assembling a virtual tour with hotspots is the abandonware, EOL Marzipano Tool, which is distinct from the open-source Marzipano Viewer.

It's really terrific; just upload your images and click around to add your hotspots, then export a .zip, and Bob's your Uncle.

The key missing feature is the complete inability to load and edit an existing project. You can modify a project that's open, and export it as many times as you want, but once you've closed your browser session, that's it. If you want to change the virtual tour, you either have to start over or start editing code by hand.

The good news is that the server-side code is very lightweight (4 MB), and available for download, and the processing is all done in-browser, so I've put a copy on my Mac, which includes a copy of Apache, so I don't have to worry about it going away someday.

But the key problem remains the inability to load an existing project. One possible workaround is to create some sort of . . . . environment? that contains both the server instance and the browser instance, so I can save the whole thing and reload it whenever I want to resume work on the project. A VM would work, of course, but that would be massive overkill. Is this was Docker is for?

What's the lightest-weight thing I could create that could run and store the server side and a Chrome browser instance?

Or is there another way to do this?

Thanks!
 

Andrewcw

Ars Legatus Legionis
18,129
Subscriptor
Your problem is the server once the client breaks connection do you lose the session. I'm guessing most web servers and web clients re-reestablish new sessions rather then try to re-use some old cached session.

I'm sure you have some VM host lying around somewhere and running two VM's or even one VM where it's the server and browser machine all in one unit and you just keep it running 24/7. You could even do as a Hyper-V instances. Just never shutoff the systems.