On Thursday, May 3, 2018 at 7:14:32 AM UTC-7, Francisco de Arriba wrote: > > We can try to move into Jupyter. But we found two new problems, how can we > do to start a Jupyter server for multiple users accounts (using a command > line like in notebook(accounts=True)) >
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. > and how can we transform .sws to a compatible extension in Jupyter? > Sage ships with a conversion tool. Sharing files between different jupyterhub users is going to be more work as well. You could equip the docker containers with a shared filesystem (your choice to make it read-only or have it writable). Alternatively, you can offer files on github or other platforms. -- 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.
