Pages

Friday, August 19, 2016

Jupyterhub

"JupyterHub is a server that gives multiple users access to Jupyter notebooks, running an independent Jupyter notebook server for each user.

To use JupyterHub, you need a Unix server (typically Linux) running somewhere that is accessible to your team on the network. The JupyterHub server can be on an internal network at your organisation, or it can run on the public internet (in which case, take care with security). Users access JupyterHub in a web browser, by going to the IP address or domain name of the server.

Different authenticators control access to JupyterHub. The default one (pam) uses the user accounts on the server where JupyterHub is running. If you use this, you will need to create a user account on the system for each user on your team. Using other authenticators, you can allow users to sign in with e.g. a Github account, or with any single-sign-on system your organisation has.

Next, spawners control how JupyterHub starts the individual notebook server for each user. The default spawner will start a notebook server on the same machine running under their system username. The other main option is to start each server in a separate container, often using Docker."

https://jupyterhub.readthedocs.io/en/latest/

https://github.com/jupyterhub/jupyterhub


How to set up Jupyter with Pyspark painlessly on AWS EC2 clusters, with S3 I/O support - https://github.com/PiercingDan/spark-Jupyter-AWS

Jupyter + Pachyderm — Part 1, Exploring and Understanding Historical Analyses - https://medium.com/pachyderm-data/jupyter-pachyderm-part-1-exploring-and-understanding-historical-analyses-2a37e56c6578

Related Software

nteract - a desktop application that allows you to develop rich documents that contain prose, executable code (in almost any language!), and images

https://github.com/nteract/nteract

dockerspawner - Spawns JupyterHub user servers in Docker container.

https://github.com/TACC/dockerspawner 

No comments:

Post a Comment