500: Internal server error when I access the data files

[Francisco de Arriba]

Hello, 

My name is Francisco, I am a Sage user since more than 5 years. In the latest versions of Sage (8.1, 8.0) in the graphical notebook (local notebook server), I have found an error that affects the versions for Ubuntu, MacOS and Windows. In a worksheet on top menu, in DATA section, when I click on "Upload or create file ..." or I click in the name of an already created data, the displayed page returns an error 500 of the server "500: Internal server error".

How can I solve this problem?

I usually use the data files for my and for students. We can create different functions set and reuse them in other worksheet and this error prevents me from using this ability.

Thank you.

[Dima Pasechnik]

sagenb is deprecated, and fixing this is a very low priority (people who wrote sagenb moved on, supporting 10+ years old  web application code is not easy at all)

Could you move on to using jupyter notebooks?

[Francisco de Arriba]

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?

[Nils Bruin]

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.

[kcrisman]

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.)

[William Stein]

A local CoCalc docker is pretty easy (just paste 2-3 lines and it
works), but the current image is really old. I wish I (or somebody)
had the time to update it (it's 100% open source). I would, but I'm
just too busy with other things right now. David Roe has run whole
Sage days with this image and it worked well, and many UW students use
some of our big servers in the basement via a (very old) local Docker
image of Cocalc running.

I can't believe there isn't also a similarly easy to use JupyterHub
docker image though, which is surely well maintained. Has anybody
looked?

All that said, I'm pretty optimistic that I (or somebody) will find
time to make a new cocalc Docker image...

-- William

>
> --
> 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...@googlegroups.com.
> To post to this group, send email to sage-s...@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-support.
> For more options, visit https://groups.google.com/d/optout.



--
William (http://wstein.org)

[David Roe]

On Thu, May 3, 2018 at 9:28 PM, William Stein <wst...@gmail.com> wrote:

On Thu, May 3, 2018 at 6:24 PM, kcrisman <kcri...@gmail.com> 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
>> 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.)

A local CoCalc docker is pretty easy (just paste 2-3 lines and it
works), but the current image is really old.  I wish I (or somebody)
had the time to update it (it's 100% open source).   I would, but I'm
just too busy with other things right now.   David Roe has run whole
Sage days with this image and it worked well, and many UW students use
some of our big servers in the basement via a (very old) local Docker
image of Cocalc running.

Code for having multiple users running on a CoCalc project with their own sage installs can be found at https://github.com/roed314/sagedays/.  I haven't been working on it, but if there are questions I'm happy to try to help.

David

I can't believe there isn't also a similarly easy to use JupyterHub
docker image though, which is surely well maintained.  Has anybody
looked?

All that said, I'm pretty optimistic that I (or somebody) will find
time to make a new cocalc Docker image...

 -- William

>
> --
> 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+unsubscribe@googlegroups.com.

[kcrisman]

I can't believe there isn't also a similarly easy to use JupyterHub
docker image though, which is surely well maintained.  Has anybody
looked?

That's kind of why I asked.

 

All that said, I'm pretty optimistic that I (or somebody) will find
time to make a new cocalc Docker image...

That would be great too.