jupyterhub.app
The multi-user notebook application
JupyterHub
jupyterhub.app.
An Application for starting a Multi-User Jupyter Notebook server.
active_server_limit
Maximum number of concurrent servers that can be active at a time.
Setting this can limit the total resources your users can consume.
An active server is any server that’s not fully stopped. It is considered active from the time it has been requested until the time that it has completely stopped.
If this many user servers are active, users will not be able to launch new servers until a server is shutdown. Spawn requests will be rejected with a 429 error asking them to try again.
If set to 0, no limit is enforced.
active_user_window
Duration (in seconds) to determine the number of active users.
activity_resolution
Resolution (in seconds) for updating activity
If activity is registered that is less than activity_resolution seconds more recent than the current value, the new value will be ignored.
This avoids too many writes to the Hub database.
admin_access
Grant admin users permission to access single-user servers.
Users should be properly informed if this is enabled.
admin_users
DEPRECATED since version 0.7.2, use Authenticator.admin_users instead.
allow_named_servers
Allow named single-user servers per user
answer_yes
Answer yes to any questions (e.g. confirm overwrite)
api_tokens
PENDING DEPRECATION: consider using services
Dict of token:username to be loaded into the database.
Allows ahead-of-time generation of API tokens for use by externally managed services, which authenticate as JupyterHub users.
Consider using services for general services that talk to the JupyterHub API.
authenticate_prometheus
Authentication for prometheus metrics
authenticator_class
Class for authenticating users.
This should be a subclass of jupyterhub.auth.Authenticator with an authenticate() method that: is a coroutine (asyncio or tornado) returns username on success, None on failure takes two arguments: (handler, data), where handler is the calling web.RequestHandler, and data is the POST form data from the login page. Changed in version 1.0: authenticators may be registered via entry points, e.g. c.JupyterHub.authenticator_class = 'pam'
This should be a subclass of jupyterhub.auth.Authenticator
jupyterhub.auth.Authenticator
with an authenticate() method that:
authenticate()
is a coroutine (asyncio or tornado)
returns username on success, None on failure
takes two arguments: (handler, data), where handler is the calling web.RequestHandler, and data is the POST form data from the login page.
handler
data
Changed in version 1.0: authenticators may be registered via entry points, e.g. c.JupyterHub.authenticator_class = 'pam'
c.JupyterHub.authenticator_class = 'pam'
default: jupyterhub.auth.PAMAuthenticator
dummy: jupyterhub.auth.DummyAuthenticator
pam: jupyterhub.auth.PAMAuthenticator
base_url
The base URL of the entire application.
Add this to the beginning of all JupyterHub URLs. Use base_url to run JupyterHub within an existing website.
bind_url
The public facing URL of the whole JupyterHub application.
This is the address on which the proxy will bind. Sets protocol, ip, base_url
cleanup_proxy
Whether to shutdown the proxy when the Hub shuts down.
Disable if you want to be able to teardown the Hub while leaving the proxy running.
Only valid if the proxy was starting by the Hub process.
If both this and cleanup_servers are False, sending SIGINT to the Hub will only shutdown the Hub, leaving everything else running.
The Hub should be able to resume from database state.
cleanup_servers
Whether to shutdown single-user servers when the Hub shuts down.
Disable if you want to be able to teardown the Hub while leaving the single-user servers running.
If both this and cleanup_proxy are False, sending SIGINT to the Hub will only shutdown the Hub, leaving everything else running.
concurrent_spawn_limit
Maximum number of concurrent users that can be spawning at a time.
Spawning lots of servers at the same time can cause performance problems for the Hub or the underlying spawning system. Set this limit to prevent bursts of logins from attempting to spawn too many servers at the same time.
This does not limit the number of total running servers. See active_server_limit for that.
If more than this many users attempt to spawn at a time, their requests will be rejected with a 429 error asking them to try again. Users will have to wait for some of the spawning services to finish starting before they can start their own.
config_file
The config file to load
confirm_no_ssl
DEPRECATED: does nothing
cookie_max_age_days
Number of days for a login cookie to be valid. Default is two weeks.
cookie_secret
The cookie secret to use to encrypt cookies.
Loaded from the JPY_COOKIE_SECRET env variable by default.
Should be exactly 256 bits (32 bytes).
cookie_secret_file
File in which to store the cookie secret.
data_files_path
The location of jupyterhub data files (e.g. /usr/local/share/jupyterhub)
db_kwargs
Include any kwargs to pass to the database connection. See sqlalchemy.create_engine for details.
db_url
url for the database. e.g. sqlite:///jupyterhub.sqlite
sqlite:///jupyterhub.sqlite
debug_db
log all database transactions. This has A LOT of output
debug_proxy
DEPRECATED since version 0.8: Use ConfigurableHTTPProxy.debug
default_server_name
If named servers are enabled, default name of server to spawn or open, e.g. by user-redirect.
default_url
The default URL for users when they arrive (e.g. when user directs to “/”)
By default, redirects users to their own server.
external_ssl_authorities
Dict authority:dict(files). Specify the key, cert, and/or ca file for an authority. This is useful for externally managed proxies that wish to use internal_ssl.
The files dict has this format (you must specify at least a cert):
{ 'key': '/path/to/key.key', 'cert': '/path/to/cert.crt', 'ca': '/path/to/ca.crt' }
The authorities you can override: ‘hub-ca’, ‘notebooks-ca’, ‘proxy-api-ca’, ‘proxy-client-ca’, and ‘services-ca’.
Use with internal_ssl
extra_handlers
Register extra tornado Handlers for jupyterhub.
Should be of the form ("<regex>", Handler)
("<regex>", Handler)
The Hub prefix will be added, so /my-page will be served at /hub/my-page.
/my-page
/hub/my-page
extra_log_file
DEPRECATED: use output redirection instead, e.g.
jupyterhub &>> /var/log/jupyterhub.log
extra_log_handlers
Extra log handlers to set on JupyterHub logger
generate_certs
Generate certs used for internal ssl
generate_config
Generate default config file
hub_bind_url
The URL on which the Hub will listen. This is a private URL for internal communication. Typically set in combination with hub_connect_url. If a unix socket, hub_connect_url must also be set.
For example:
“http://127.0.0.1:8081” “unix+http://%2Fsrv%2Fjupyterhub%2Fjupyterhub.sock”
New in version 0.9.
hub_connect_ip
The ip or hostname for proxies and spawners to use for connecting to the Hub.
Use when the bind address (hub_ip) is 0.0.0.0, :: or otherwise different from the connect address.
hub_ip
Default: when hub_ip is 0.0.0.0 or ::, use socket.gethostname(), otherwise use hub_ip.
socket.gethostname()
Note: Some spawners or proxy implementations might not support hostnames. Check your spawner or proxy documentation to see if they have extra requirements.
New in version 0.8.
hub_connect_port
DEPRECATED
Use hub_connect_url
Deprecated since version 0.9: Use hub_connect_url
hub_connect_url
The URL for connecting to the Hub. Spawners, services, and the proxy will use this URL to talk to the Hub.
Only needs to be specified if the default hub URL is not connectable (e.g. using a unix+http:// bind url).
See also
JupyterHub.hub_connect_ip JupyterHub.hub_bind_url
The ip address for the Hub process to bind to.
By default, the hub listens on localhost only. This address must be accessible from the proxy and user servers. You may need to set this to a public ip or ‘’ for all interfaces if the proxy or user servers are in containers or on a different host.
See hub_connect_ip for cases where the bind and connect address should differ, or hub_bind_url for setting the full bind URL.
hub_port
The internal port for the Hub process.
This is the internal port of the hub itself. It should never be accessed directly. See JupyterHub.port for the public port to use when accessing jupyterhub. It is rare that this port should be set except in cases of port conflict.
See also hub_ip for the ip and hub_bind_url for setting the full bind URL.
implicit_spawn_seconds
Trigger implicit spawns after this many seconds.
When a user visits a URL for a server that’s not running, they are shown a page indicating that the requested server is not running with a button to spawn the server.
Setting this to a positive value will redirect the user after this many seconds, effectively clicking this button automatically for the users, automatically beginning the spawn process.
Warning: this can result in errors and surprising behavior when sharing access URLs to actual servers, since the wrong server is likely to be started.
init_spawners_timeout
Timeout (in seconds) to wait for spawners to initialize
Checking if spawners are healthy can take a long time if many spawners are active at hub start time.
If it takes longer than this timeout to check, init_spawner will be left to complete in the background and the http server is allowed to start.
A timeout of -1 means wait forever, which can mean a slow startup of the Hub but ensures that the Hub is fully consistent by the time it starts responding to requests. This matches the behavior of jupyterhub 1.0.
internal_certs_location
The location to store certificates automatically created by JupyterHub.
internal_ssl
Enable SSL for all internal communication
This enables end-to-end encryption between all JupyterHub components. JupyterHub will automatically create the necessary certificate authority and sign notebook certificates as they’re created.
ip
The public facing ip of the whole JupyterHub application (specifically referred to as the proxy).
This is the address on which the proxy will listen. The default is to listen on all interfaces. This is the only address through which JupyterHub should be accessed by users.
jinja_environment_options
Supply extra arguments that will be passed to Jinja environment.
last_activity_interval
Interval (in seconds) at which to update last-activity timestamps.
load_groups
Dict of ‘group’: [‘usernames’] to load at startup.
This strictly adds groups and users to groups.
Loading one set of groups, then starting JupyterHub again with a different set will not remove users or groups from previous launches. That must be done through the API.
log_datefmt
The date format used by logging formatters for %(asctime)s
log_format
The Logging format template
log_level
Set the log level by value or name.
logo_file
Specify path to a logo image to override the Jupyter logo in the banner.
named_server_limit_per_user
Maximum number of concurrent named servers that can be created by a user at a time.
Setting this can limit the total resources a user can consume.
pid_file
File to write PID Useful for daemonizing JupyterHub.
port
The public facing port of the proxy.
This is the port on which the proxy will listen. This is the only port through which JupyterHub should be accessed by users.
proxy_api_ip
DEPRECATED since version 0.8 : Use ConfigurableHTTPProxy.api_url
proxy_api_port
proxy_auth_token
DEPRECATED since version 0.8: Use ConfigurableHTTPProxy.auth_token
proxy_check_interval
Interval (in seconds) at which to check if the proxy is running.
proxy_class
The class to use for configuring the JupyterHub proxy.
Should be a subclass of jupyterhub.proxy.Proxy. Changed in version 1.0: proxies may be registered via entry points, e.g. c.JupyterHub.proxy_class = 'traefik'
Should be a subclass of jupyterhub.proxy.Proxy.
jupyterhub.proxy.Proxy
Changed in version 1.0: proxies may be registered via entry points, e.g. c.JupyterHub.proxy_class = 'traefik'
c.JupyterHub.proxy_class = 'traefik'
configurable-http-proxy: jupyterhub.proxy.ConfigurableHTTPProxy
default: jupyterhub.proxy.ConfigurableHTTPProxy
proxy_cmd
DEPRECATED since version 0.8. Use ConfigurableHTTPProxy.command
recreate_internal_certs
Recreate all certificates used within JupyterHub on restart.
Note: enabling this feature requires restarting all notebook servers.
redirect_to_server
Redirect user to server (if running), instead of control panel.
reset_db
Purge and reset the database.
service_check_interval
Interval (in seconds) at which to check connectivity of services with web endpoints.
service_tokens
Dict of token:servicename to be loaded into the database.
Allows ahead-of-time generation of API tokens for use by externally managed services.
services
List of service specification dictionaries.
A service
For instance:
services = [ { 'name': 'cull_idle', 'command': ['/path/to/cull_idle_servers.py'], }, { 'name': 'formgrader', 'url': 'http://127.0.0.1:1234', 'api_token': 'super-secret', 'environment': } ]
shutdown_on_logout
Shuts down all user servers on logout
spawner_class
The class to use for spawning single-user servers.
Should be a subclass of jupyterhub.spawner.Spawner. Changed in version 1.0: spawners may be registered via entry points, e.g. c.JupyterHub.spawner_class = 'localprocess'
Should be a subclass of jupyterhub.spawner.Spawner.
jupyterhub.spawner.Spawner
Changed in version 1.0: spawners may be registered via entry points, e.g. c.JupyterHub.spawner_class = 'localprocess'
c.JupyterHub.spawner_class = 'localprocess'
default: jupyterhub.spawner.LocalProcessSpawner
localprocess: jupyterhub.spawner.LocalProcessSpawner
simple: jupyterhub.spawner.SimpleLocalProcessSpawner
ssl_cert
Path to SSL certificate file for the public facing interface of the proxy
When setting this, you should also set ssl_key
ssl_key
Path to SSL key file for the public facing interface of the proxy
When setting this, you should also set ssl_cert
statsd_host
Host to send statsd metrics to. An empty string (the default) disables sending metrics.
statsd_port
Port on which to send statsd metrics about the hub
statsd_prefix
Prefix to use for all metrics sent by jupyterhub to statsd
subdomain_host
Run single-user servers on subdomains of this host.
This should be the full https://hub.domain.tld[:port].
https://hub.domain.tld[:port]
Provides additional cross-site protections for javascript served by single-user servers.
Requires <username>.hub.domain.tld to resolve to the same host as hub.domain.tld.
<username>.hub.domain.tld
hub.domain.tld
In general, this is most easily achieved with wildcard DNS.
When using SSL (i.e. always) this also requires a wildcard SSL certificate.
template_paths
Paths to search for jinja templates, before using the default templates.
template_vars
Extra variables to be passed into jinja templates
tornado_settings
Extra settings overrides to pass to the tornado application.
trust_user_provided_tokens
Trust user-provided tokens (via JupyterHub.service_tokens) to have good entropy.
If you are not inserting additional tokens via configuration file, this flag has no effect.
In JupyterHub 0.8, internally generated tokens do not pass through additional hashing because the hashing is costly and does not increase the entropy of already-good UUIDs.
User-provided tokens, on the other hand, are not trusted to have good entropy by default, and are passed through many rounds of hashing to stretch the entropy of the key (i.e. user-provided tokens are treated as passwords instead of random keys). These keys are more costly to check.
If your inserted tokens are generated by a good-quality mechanism, e.g. openssl rand -hex 32, then you can set this flag to True to reduce the cost of checking authentication tokens.
openssl rand -hex 32
trusted_alt_names
Names to include in the subject alternative name.
These names will be used for server name verification. This is useful if JupyterHub is being run behind a reverse proxy or services using ssl are on different hosts.
trusted_downstream_ips
Downstream proxy IP addresses to trust.
This sets the list of IP addresses that are trusted and skipped when processing the X-Forwarded-For header. For example, if an external proxy is used for TLS termination, its IP address should be added to this list to ensure the correct client IP addresses are recorded in the logs instead of the proxy server’s IP address.
X-Forwarded-For
upgrade_db
Upgrade the database automatically on start.
Only safe if database is regularly backed up. Only SQLite databases will be backed up to a local file automatically.
user_redirect_hook
Callable to affect behavior of /user-redirect/
Receives 4 parameters: 1. path - URL path that was provided after /user-redirect/ 2. request - A Tornado HTTPServerRequest representing the current request. 3. user - The currently authenticated user. 4. base_url - The base_url of the current hub, for relative redirects
It should return the new URL to redirect to, or None to preserve current behavior.