--
You received this message because you are subscribed to the Google Groups "Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jupyter+unsubscribe@googlegroups.com.
To post to this group, send email to jup...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jupyter/ddf1de17-71be-47ee-b9e4-2d8038500b1f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
ThomasThis is the first time I've done anything with Jupyterhub or Vagrant, so don't take any of that as the best way to do things!I'm assembling this in a VM using Vagrant. You can see the files I'm using to set this up here:Hi Tony,Yes! I'm setting up something quite similar here, where we initially want the functionality of tmpnb but might want the functionality of Jupyterhub later. At Min's suggestion, I am putting together something a lot like tmpnb using tmpauthenticator and dockerspawner:
https://github.com/jupyterhub/tmpauthenticator/
https://github.com/jupyterhub/dockerspawner
https://github.com/joommf/try-joommf-deploy
On 11 September 2017 at 12:58, Tony Hirst <tony....@gmail.com> wrote:
HiI'm trying to lobby my institution into setting up a hosted Jupyter notebook server to support a v small activity (2 notebooks, 15-30 mins per notebook) as part of a course serving maybe 1500 students.My gut feeling is to suggest tmpb because I assume that's the simplest thing to manage, but I was wondering if there is a way of configuring Jupyterhub to act as a tmpnb server (no persisted notebooks, no need for use logins, all sessions independent)?If there is, Jupyterhub perhaps offers a better option because then I can start working on folk to support user accounts without them having to go through the process of figuring out how to deply and support yet another installation.Related to this, does anyone have roadmaps to adoption that can be presented to reluctant IT folk as part of a Jupyter advocacy plan? ;-)--tony
--
You received this message because you are subscribed to the Google Groups "Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jupyter+u...@googlegroups.com.
..... so: I get Jupyterhub asking for user/pwd credentials on :8081? (In passing, I also note it's offering a warning about 'should use https')
PS by the by - are you at Southampton? Would be good to ry to grab a coffee at some point if so... (are you ever on IW?)
--
You received this message because you are subscribed to the Google Groups "Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jupyter+unsubscribe@googlegroups.com.
To post to this group, send email to jup...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jupyter/56e7e528-ca2c-49c6-b219-06c3b68f2038%40googlegroups.com.
You will need to bypass a self-signed cert warning to see the page.I think I made a mistake in the config file which prevented any config from taking effect. Try pulling again now and going to:https://127.0.0.1:8000
On 11 September 2017 at 17:20, Tony Hirst <tony....@gmail.com> wrote:
I simply downloaded the repo and did a vagrant up and it gave me the login screen. Will try to have a poke around to see if I can figure out why..--tony
On Monday, 11 September 2017 15:28:33 UTC+1, takowl wrote:On 11 September 2017 at 15:16, Tony Hirst <tony....@gmail.com> wrote:..... so: I get Jupyterhub asking for user/pwd credentials on :8081? (In passing, I also note it's offering a warning about 'should use https')It shouldn't ask for credentials with this configuration - tmpauthenticator should just direct each user to a new container. It's working as expected for me, but I may have done some things which are brittle.I'm working on the https part at the moment - my configuration will use a self-signed cert, because the university is going to put it behind their load balancer which should have a proper SSL cert.PS by the by - are you at Southampton? Would be good to ry to grab a coffee at some point if so... (are you ever on IW?)Yup, I am at Southampton, and I also go across to the IW from time to time on weekends - mostly to Cowes. I'd be happy to meet up for coffee in either place - feel free to ping me off list.
--
You received this message because you are subscribed to the Google Groups "Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jupyter+u...@googlegroups.com.
To post to this group, send email to jup...@googlegroups.com.
thx - works fine now... this could well be a better approach for us, as long as we can get s/thing working that scales w/ resource IT folk are happy to commit.... (will have 1-2k users arriving over a 1-2 week period and Sod's law they'd do it at same time ;-)
--
You received this message because you are subscribed to the Google Groups "Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jupyter+unsubscribe@googlegroups.com.
To post to this group, send email to jup...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jupyter/4c9c4b58-9b43-4e2e-845b-4f39439873f0%40googlegroups.com.
As one of the original tmpnb authors, I wholeheartedly endorse JupyterHub + tmpauthenticator + dockerspawner as the Official Best Way to do tmpnb style deployments for the far future. 🤔 I wonder if we should turn jupyter/tmpnb into just that -- an opinionated JupyterHub deployment.
----On Tue, Sep 12, 2017 at 8:04 AM, Tony Hirst <tony....@gmail.com> wrote:Ah - so those fixes were pushed to Jupyterhub repo?--That sounds as if it's best plan for us, I think.--tony
On Monday, 11 September 2017 20:50:20 UTC+1, Yuvi Panda wrote:We run a ~1500 student JupyterHub for our class at Berkeley
(data.berkeley.edu) based on https://z2jh.jupyter.org :) We're pretty
much at 0 hub related issues about a week in :)
You can set it up to use tmpauthenticator, but can also use other
authentication methods if need be. We've done a bunch of stress tests,
and fixed a lot of the issues (especially the 'too many redirects'
issue) in 0.8.
You received this message because you are subscribed to the Google Groups "Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jupyter+unsubscribe@googlegroups.com.
To post to this group, send email to jup...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jupyter/4c9c4b58-9b43-4e2e-845b-4f39439873f0%40googlegroups.com.Kyle Kelley (@rgbkrk; lambdaops.com)
You received this message because you are subscribed to the Google Groups "Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jupyter+unsubscribe@googlegroups.com.
To post to this group, send email to jup...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jupyter/CA%2BtbMaVvo%3Dx1FsJpo_GtNkezbx-_q0FM9j9s-y5eM1M_35tX-g%40mail.gmail.com.
On Tue, Sep 12, 2017 at 8:52 AM, Kyle Kelley <rgb...@gmail.com> wrote:As one of the original tmpnb authors, I wholeheartedly endorse JupyterHub + tmpauthenticator + dockerspawner as the Official Best Way to do tmpnb style deployments for the far future. 🤔 I wonder if we should turn jupyter/tmpnb into just that -- an opinionated JupyterHub deployment.It is my plan to do exactly this when I get a chance. It would be even better if somebody else does it first!