Dave, can you share basic instructions how you achieved this hybrid Linux/Windows jupyterhub setup?
Another way would be to rely on WSL in Windows 10 completely: https://github.com/Microsoft/BashOnWindows/issues/185 On Tuesday, June 27, 2017 at 5:16:59 PM UTC-5, Dave Hirschfeld wrote: > > JupyterHub might [1]_ require *nix but that doesn't mean it's can't spawn > containers on remote Windows servers - in fact that's exactly what I'm > doing now. I haven't gotten around to the load-balancing part but I assume > that could be done with Docker Swarm or I'm considering Windows HPC for its > ability to burst to Azure. > > > .. [1] Having discussed with @minrk it's quite possible if your'e not > using the default linux only authentication that you can run JupyterHub on > Windows. I'm using the LDAP authenticator so I'll be giving that a go to > avoid the hassle of spinning up an Ubuntu VM on Hyper-V. > > > HTH, > Dave > > > On Tuesday, 27 June 2017 03:28:14 UTC+10, Pav A wrote: >> >> JupyterHub and tmpnb are unix only, so, unfortunately these are not an >> option. >> >> What would be the best approach to load-balance Jupyter kernels on >> Windows? A reverse proxy to a collection of host/ports is trivial, but the >> objective is to channel http and ws traffic pertaining to a particular >> kernel to a particular host. >> >> What's the best way to hook it up to kernel_gateway/nb2kg? >> >> -- 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/2890ae6b-76de-4432-8e05-e13f2120452a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
