3 ms·

I did some research a short while ago but I’ve forgotten it all - but does too or any like it do persistence? I.e. I can close the window and reopen and see the

I did some research a short while ago but I’ve forgotten it all - but does too or any like it do persistence? I.e. I can close the window and reopen and see the same stuff that was just there? My use case is starting long running processes - namely machine learning instances and having multiple people monitor through a browser and be able to close/reopen the window to check progress. I do this currently using a jupyter notebook terminal but I’d like to not use jupyter notebooks at all if possible. Screen / tmux etc is just too big a barrier for this unfortunately.

qbasic_forever 5y ago
No, what you're asking for is exactly what screen and tmux were designed to do though. In the not too distant past many online services (frontend servers, databases, etc.) were basically just run out of tmux instances so different sysadmins could connect and monitor them, redeploy them, etc. It's a basic form of interactive process management which is what you're after. I agree tmux especially can get pretty complex and frightful to learn. However just learn the basics of creating a session, exiting, and re-entering a session and you will be golden. Ignore all the fancy stuff like window splitting, layout, etc. until you need it. edit: What you could do perhaps though is have a tool like GoTTY launch into your tmux session directly and attach to it instead of launching a plain bash or login shell. This way the less technical folks wouldn't have to remember how to use tmux. As far as they're concerned whenever they open the webpage they connect back to the running process.
hoherd 5y ago
Have you tried tmate? It's tmux, but accessible online via browser or ssh in rw or ro mode. It's also self-hostable.