JupyterHub is the best way to serve Jupyter notebook for multiple users. It can be used in a classes of students, a corporate data science group or scientific research group. It is a multi-user Hub that spawns, manages, and proxies multiple instances of the single-user Jupyter notebook server.
Documentation at https://melpa.org/#/jupyter
JupyterHub: A multi-user server for Jupyter notebooks
An extensible environment for interactive and reproducible computing, based on the Jupyter Notebook and Architecture.
This package provides an Emacs interface to communicate with Jupyter kernels. It provides REPL and Org mode source code block frontends to Jupyter kernels and kernel interactions integrated with Emacs' built-in features.
The backend—i.e. core services, APIs, and REST endpoints—to Jupyter web applications.
Documentation at https://melpa.org/#/jupyter-ascending
The Littlest JupyterHub (TLJH) distribution helps you provide Jupyter Notebooks to 1-50 users on a single server. Administrators who do not consider themselves 'system administrators' but would like to provide hosted Jupyter Notebooks for their students / users are the primary audience. All users are provided with the same environment, and administrators can easily install libraries into this environment without any specialized knowledge.
Jupyter telemetry library
repo2docker
fetches a git repository and builds a container image based on the configuration files found in the repository.
Jupyter Server Proxy lets you run arbitrary external processes (such as RStudio, Shiny Server, Syncthing, PostgreSQL, Code Server, etc) alongside your notebook server and provide authenticated web access to them using a path like /rstudio
next to others like /lab
. Alongside the python package that provides the main functionality, the JupyterLab extension (@jupyterlab/server-proxy
) provides buttons in the JupyterLab launcher window to get to RStudio for example.
Jupyter Server Proxy lets you run arbitrary external processes (such as RStudio, Shiny Server, Syncthing, PostgreSQL, Code Server, etc) alongside your notebook server and provide authenticated web access to them using a path like /rstudio
next to others like /lab
. Alongside the python package that provides the main functionality, the JupyterLab extension (@jupyterlab/server-proxy
) provides buttons in the JupyterLab launcher window to get to RStudio for example.
An implementation of the JupyterHub proxy api with traefik: an extremely lightweight, portable reverse proxy implementation, that supports load balancing and can configure itself automatically and dynamically.
LDAP Authenticator for JupyterHub