On Sun, 21 Oct 2018 21:20:33 -0500 "Edward K. Ream" <edream...@gmail.com> wrote:
> Hmm. Is Leo as a web app is feasible? Leo's scripting features make > it extremely dangerous. If run on a server, Leo becomes an > unverifiable cgi script. This looks like a gotcha. Am I missing > something? Sandboxing / encapsulation with Docker or some similar container system seems like the easy way. Containers are much lighter than VMs, so you should be able to run many sessions, depending on hardware etc. Docker containers start fast enough if you're running something long-lived like a session on leoBridge.py or something that runs for the same length of time as a typical Leo session. I *think* they'd be too slow to exist transiently and respond to single requests, although maybe hot cache on a suitable machine could run that way. But I'm guessing you're looking for something more persistent, anyway. I just tried starting a Docker environment I have based on conda/miniconda3 which is based on debian, and it starts in under a second. It has tex-live / numpy / matplotlib (which pulls in a chunk of Qt), so it's probably similar in size to something that would run Leo. Cheers -Terry -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
