Skip to content
Simple JupyterHub distribution for 1-100 users on a single server
Branch: master
Clone or download
yuvipanda Merge pull request #294 from story645/patch-1
DOC: moved nativeauthentic config instructions to code block
Latest commit 9809009 Mar 15, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
.circleci Replace chp with traefik-proxy Feb 13, 2019
docs moved nativeauthentic config to code block Mar 14, 2019
integration-tests Generate random traefik api password Feb 13, 2019
tests Merge branch 'master' into replace_chp_traefik Feb 22, 2019
tljh Pin tornado in user env Mar 8, 2019
.gitignore Initial commit Jun 15, 2018
LICENSE Initial commit Jun 15, 2018 include traefik template in MANIFEST Jul 30, 2018
README.rst Fixing RTD badge Nov 30, 2018
dev-requirements.txt Generate random traefik api password Feb 13, 2019 Use the actual installation path of chp service, changed traefik-prox… Feb 19, 2019


The Littlest JupyterHub

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 get the same environment, and administrators can install libraries into this environment without any specialized knowledge. It provides all users with the same environment, and administrators can install libraries into this environment easily without any specialized knowledge.

See this blog post for more information.

Development Status

This project is currently in alpha state. Most things work, but we might still make breaking changes that have no clear upgrade pathway. We are targeting a v0.1 release sometime in mid-August 2018. Follow this milestone to see progress towards the release!


The Littlest JupyterHub (TLJH) can run on any server that is running at least Ubuntu 18.04. We have a bunch of tutorials to get you started!


Our latest documentation is at:

We place a high importance on consistency, readability and completeness of documentation. If a feature is not documented, it does not exist. If a behavior is not documented, it is a bug! We try to treat our documentation like we treat our code: we aim to improve it as often as possible.

If something is confusing to you in the documentation, it is a bug. We would be happy if you could file an issue about it - or even better, contribute a documentation fix!

You can’t perform that action at this time.