Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Public interfacing for sharing, etc. #17
Sorry that I got cut off from the ipython-dev discussion this afternoon... my house lost internet access.
Anyway, I'll make some notes here about the public/sharing aspects of the jupyterhub:
The public handler should be able to:
Here is a prototype of some of the ideas:
IPython priorities, from my perspective:
I have some other aspects I need to wrestle with (how do they get a kernel installed easily, how do they get some nbextensions), but that is mostly me figuring out details to instruct the class).
It would be very handy to have sharing work similarly to Google Docs:
But I also like a browsable public view, such as:
(My students are starting to create their own sharable/collaborative "notebooks"... they are making notebook cells be cells in a Google Spreadsheet, and working on ways to migrate between the spreadsheet and the notebook. Clever idea!)
Here is the older gist:
and a more developed version:
Yes, I think we do want to provide a version of this. The question is how do we do it with the current abstractions, where the Hub doesn't know anything about the single-user files. @dsblank's implementation makes convenient assumptions about the filesystem for their deployment that we can't make in general. So we need a mechanism for single-user servers to publish notebooks to the Hub, and for the Hub to store them somewhere.
If this can be done as a separate 'sharing service', I think that would be ideal, perhaps as a peer to Spawner and Authenticator.
cc @TimShawver who worked on most of this in our codebase.