Re: [sage-devel] Re: From SageNB to jupyter
On Thu, 7 Sep 2017, Dima Pasechnik wrote: did you see this:https://benjamin-hackl.at/2016/01/16/jupyterhub-with-sagemath-kernel/ It seems that all of the requirements you list are there... Not sharing notebooks, but it seems that it has been done later: https://github.com/jupyterhub/hubshare/issues/15 Maybe I wait for this to stabilize and then try to install all parts and see if it works. -- Jori Mäntysalo
[sage-devel] Re: From SageNB to jupyter
On Saturday, September 9, 2017 at 6:54:38 PM UTC-4, Enrique Artal wrote: > > It is a server with 8 cores and 32GB of RAM, but with several other sagenb > processes and twenty users on jupyterhub plus 60 on the sagenb instances > cause no performance issue (usually) > Oh yeah, 32 GB would be plenty :) -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Re: From SageNB to jupyter
It is a server with 8 cores and 32GB of RAM, but with several other sagenb processes and twenty users on jupyterhub plus 60 on the sagenb instances cause no performance issue (usually) El sábado, 9 de septiembre de 2017, 15:03:53 (UTC+2), kcrisman escribió: > > > > On Saturday, September 9, 2017 at 6:12:49 AM UTC-4, Enrique Artal wrote: >> >> It is quite useful, indeed. We have installed it in our servers. >> > > Could it be made "even easier" to deploy? Sagenb really just required > someone who knew how to give things a domain name and commands to start a > server. > > Also, more formal testing of the requirements for memory would be helpful > - many local sagenb installs only had a couple gig of RAM available on a > virtual machine and so couldn't handle more than a dozen or so users at a > time. > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Re: From SageNB to jupyter
On Saturday, September 9, 2017 at 6:12:49 AM UTC-4, Enrique Artal wrote: > > It is quite useful, indeed. We have installed it in our servers. > Could it be made "even easier" to deploy? Sagenb really just required someone who knew how to give things a domain name and commands to start a server. Also, more formal testing of the requirements for memory would be helpful - many local sagenb installs only had a couple gig of RAM available on a virtual machine and so couldn't handle more than a dozen or so users at a time. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Re: From SageNB to jupyter
It is quite useful, indeed. We have installed it in our servers. El viernes, 8 de septiembre de 2017, 16:48:49 (UTC+2), kcrisman escribió: > > > > On Thursday, September 7, 2017 at 11:16:14 AM UTC-4, Dima Pasechnik wrote: >> >> did you see this: >> https://benjamin-hackl.at/2016/01/16/jupyterhub-with-sagemath-kernel/ >> >> It seems that all of the requirements you list are there... >> > > This seems very interesting, especially if it could be packaged up in a > box, so to speak, for deployment. > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: From SageNB to jupyter
On Friday, September 8, 2017 at 2:04:24 AM UTC-4, Jori Mäntysalo wrote: > > On Thu, 7 Sep 2017, Volker Braun wrote: > > > You can share worksheets just by uploading them to github, for example: > > Isn't that publishing worksheet, not sharing? > Yeah, that's really quite different and more involved. It's true that no one who has time and expertise will be working much on sagenb, it appears. But it does have features which still aren't easily available in something people can "just put up there" so I agree there isn't a drop-in replacement yet, and a few of us will try to give advice as we are able. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Re: From SageNB to jupyter
On Thursday, September 7, 2017 at 11:16:14 AM UTC-4, Dima Pasechnik wrote: > > did you see this: > https://benjamin-hackl.at/2016/01/16/jupyterhub-with-sagemath-kernel/ > > It seems that all of the requirements you list are there... > This seems very interesting, especially if it could be packaged up in a box, so to speak, for deployment. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: From SageNB to jupyter
well, in principle you can put it in a private repo, and control access to it the github way. Although I agree this is not very easy as opposed to sagenb or SMC worksheet sharing. On Friday, September 8, 2017 at 7:04:24 AM UTC+1, Jori Mäntysalo wrote: > > On Thu, 7 Sep 2017, Volker Braun wrote: > > > You can share worksheets just by uploading them to github, for example: > > Isn't that publishing worksheet, not sharing? > > -- > Jori Mäntysalo -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: From SageNB to jupyter
On Thu, 7 Sep 2017, Volker Braun wrote: You can share worksheets just by uploading them to github, for example: Isn't that publishing worksheet, not sharing? -- Jori Mäntysalo
[sage-devel] Re: From SageNB to jupyter
You can share worksheets just by uploading them to github, for example: http://nbviewer.jupyter.org/github/vbraun/torsion_cup_product/blob/master/Y0_cohomology_ring.ipynb https://github.com/vbraun/torsion_cup_product/blob/master/Y0_cohomology_ring.ipynb On Thursday, September 7, 2017 at 1:56:35 PM UTC+2, Enrique Artal wrote: > > And probably the ability of sharing worksheets, I did not find it in > jupyter or jupyterhub; of course SMC would be OK but I see only the option > of campus accounts or personal docker copies. > > El jueves, 7 de septiembre de 2017, 13:32:02 (UTC+2), Jori Mäntysalo > escribió: >> >> On Thu, 7 Sep 2017, Dima Pasechnik wrote: >> >> > What exactly are you missing from jupyter nb, or jupyter hub, or some >> version of SMC >> > people managed to get running on their intranets? >> >> I don't actually know; SageNB has just been a working piece of software. >> >> What we need is >> >> - User management from LDAP or Shibboleth, so that everyone with an >> account on them can just sign in to Sage. >> - Local user accounts too. >> - Security, so that a user A can not see worksheets for user B. >> - Importing SageNB worksheet to a new system worksheet. >> >> -- >> Jori Mäntysalo > > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Re: From SageNB to jupyter
did you see this: https://benjamin-hackl.at/2016/01/16/jupyterhub-with-sagemath-kernel/ It seems that all of the requirements you list are there... On Thursday, September 7, 2017 at 12:32:02 PM UTC+1, Jori Mäntysalo wrote: > > On Thu, 7 Sep 2017, Dima Pasechnik wrote: > > > What exactly are you missing from jupyter nb, or jupyter hub, or some > version of SMC > > people managed to get running on their intranets? > > I don't actually know; SageNB has just been a working piece of software. > > What we need is > > - User management from LDAP or Shibboleth, so that everyone with an > account on them can just sign in to Sage. > - Local user accounts too. > - Security, so that a user A can not see worksheets for user B. > - Importing SageNB worksheet to a new system worksheet. > > -- > Jori Mäntysalo -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Re: From SageNB to jupyter
And probably the ability of sharing worksheets, I did not find it in jupyter or jupyterhub; of course SMC would be OK but I see only the option of campus accounts or personal docker copies. El jueves, 7 de septiembre de 2017, 13:32:02 (UTC+2), Jori Mäntysalo escribió: > > On Thu, 7 Sep 2017, Dima Pasechnik wrote: > > > What exactly are you missing from jupyter nb, or jupyter hub, or some > version of SMC > > people managed to get running on their intranets? > > I don't actually know; SageNB has just been a working piece of software. > > What we need is > > - User management from LDAP or Shibboleth, so that everyone with an > account on them can just sign in to Sage. > - Local user accounts too. > - Security, so that a user A can not see worksheets for user B. > - Importing SageNB worksheet to a new system worksheet. > > -- > Jori Mäntysalo -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Re: From SageNB to jupyter
On Thu, 7 Sep 2017, Dima Pasechnik wrote: What exactly are you missing from jupyter nb, or jupyter hub, or some version of SMC people managed to get running on their intranets? I don't actually know; SageNB has just been a working piece of software. What we need is - User management from LDAP or Shibboleth, so that everyone with an account on them can just sign in to Sage. - Local user accounts too. - Security, so that a user A can not see worksheets for user B. - Importing SageNB worksheet to a new system worksheet. -- Jori Mäntysalo
