Re: [sage-support] Re: 500: Internal server error when I access the data files

On Thu, May 3, 2018 at 9:28 PM, William Stein wrote: > On Thu, May 3, 2018 at 6:24 PM, kcrisman wrote: > > > >> The standard solution is Jupyterhub. That's a non-trivial undertaking to > >> set up, though. The processes for the users run in dedicated docker

Re: [sage-support] Re: 500: Internal server error when I access the data files

On Thu, May 3, 2018 at 6:24 PM, kcrisman wrote: > >> 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 >>

[sage-support] Re: 500: Internal server error when I access the data files

> 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

[sage-support] Re: Right way to kill notebook server on single-user machine

Nope -- or at least, not for me. "jupyter notebook list" works fine, but "jupyter notebook stop " returns an error indicating that the file stop can not be found... Perhaps this feature has been dropped? This approach also appears to be slow, presumably due to overhead when starting

[sage-support] Re: Right way to kill notebook server on single-user machine

On Thursday, May 3, 2018 at 2:32:22 PM UTC-7, Tevian Dray wrote: > > Finally had a chance to test this; yes it works -- although it is > apparently possible to send the two kill commands too close together. Thank > you very much. Have to say it's a bit of a kluge, though -- the design >

[sage-support] Re: Right way to kill notebook server on single-user machine

Finally had a chance to test this; yes it works -- although it is apparently possible to send the two kill commands too close together. Thank you very much. Have to say it's a bit of a kluge, though -- the design assumption that notebooks will always be started in shell windows that stay open

[sage-support] Re: 500: Internal server error when I access the data files

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

[sage-support] Re: 500: Internal server error when I access the data files

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)) and how can we transform .sws to a compatible extension in Jupyter? El viernes, 27 de abril de 2018,