> The standard solution is Jupyterhub. That's a non-trivial undertaking to > set up, though. The processes for the users run in dedicated docker > containers. sagenb was a lot easier for this, but never properly secure. I > wouldn't dare asking a sysadmin to deploy a sagenb server. Jupyterhub is > quite well-engineered. >
That's as may be, but it worked, easily, and properly sandboxed it was never really that kind of security risk, from what I understand (assuming one didn't allow published worksheets, which as is known were much easier to cause trouble with). I really wish that we could have held on to a little more developer interest for maintaining sagenb until Juypterhub was "stupid easy" to use. Would a local CoCalc Docker install for multiple users be any easier to set up than JH, or worse? (I assume harder, but that's not a very informed thought.) -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-support+unsubscr...@googlegroups.com. To post to this group, send email to sage-support@googlegroups.com. Visit this group at https://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/d/optout.
