Being able to launch different notebook servers is orthogonal to one user being able to launch multiple notebook servers simultaneously. In the former scenario, a user can start a notebook server with one set of libraries, extensions, and executables, then shut it down and start up a different notebook server with access to different features. That is possible with containers though I imagine you could approximate it by preparing separate venvs or envs. Whether you choose containers or tailored environments, you could give your users a choice by exposing an options form <http://jupyterhub.readthedocs.io/en/latest/reference/spawners.html?highlight=options%20form#> .
-- 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/533839f6-f380-4676-8077-762644a08477%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
