Michael, hello.
On 22 Mar 2018, at 18:41, Michael Milligan wrote:
My suspicion is that this is going to be more finicky than you would
like.
[snip]
Hmm: it does sound like it, from what you say.
I think, on reflection, that although it would be nice to have the two
services running in parallel, it's probably not urgent enough to warrant
the extra complication, and I'll simply change the config after the end
of the semester. People can live with an ugly URL for a couple more
months!
Personally, I would just run a single Jupyterhub stack (without SSL)
behind
nginx, and also have nginx or the Proxy (see "--redirect-port" at
https://github.com/jupyterhub/configurable-http-proxy) serve a
redirect
from port 8000 to the nginx endpoint.
That's pretty much my plan, with nginx (my first late-to-the-party
experience with nginx, which is suddenly My New Favourite Webserver),
and I've got that working on a test server. That was surprisingly
painless. Thanks for confirming that there are no obvious bear-traps
with this setup.
Best wishes,
Norman
--
Norman Gray : https://nxg.me.uk
--
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jupyter/D2EA9E9F-6257-4CAC-9FC9-FF078353CDC9%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
