Deploying JupyterHub at your institution

pyenv is really interesting… but confusing to a novice? I guess one trick is for us to distribute things that way and to try to provide self-contained envts that work? But things become problematic if folk end up in another env? So we need good ways of signalling that to them?

By the by, this whole UI thing reminds me of this thread on a desktop Binderhub / repo2docker GUI: What would a repo2docker GUI look like?

That can provide another way of getting an environment onto a desktop, although with the Docker requirement (and again: for users on Windows 8, that is problematic…)

1 Like