From 17f1346c08546f9048a7b3f9ab55833f5407f683 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ozan=20=C3=87a=C4=9Flayan?= Date: Wed, 4 May 2016 18:15:15 +0300 Subject: [PATCH] doc: address reviewers comments --- docs/source/getting-started.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/source/getting-started.md b/docs/source/getting-started.md index 37f996e8..eed9a6ba 100644 --- a/docs/source/getting-started.md +++ b/docs/source/getting-started.md @@ -344,11 +344,11 @@ which is the place to put configuration that you want to affect all of your user ## External services -JupyterHub has a REST API that can be used to run external services like the +JupyterHub has a REST API that can be used by external services like the [cull_idle_servers](https://github.com/jupyterhub/jupyterhub/blob/master/examples/cull-idle/cull_idle_servers.py) script which monitors and kills idle single-user servers periodically. In order to run such an -external service, you need to provide it an API token that - for the above example - is passed -through an environment variable called `JPY_API_TOKEN`. +external service, you need to provide it an API token. In the case of `cull_idle_servers`, it is passed +as the environment variable called `JPY_API_TOKEN`. Currently there are two ways of registering that token with JupyterHub. The first on is to use the `jupyterhub` command to generate a token for a specific hub user: @@ -370,7 +370,7 @@ and then write it to your JupyterHub configuration file (note that the **key** i c.JupyterHub.api_tokens = {'token' : 'username'} ``` -Upon restarting the daemon, you should see a message like below in the logs: +Upon restarting JupyterHub, you should see a message like below in the logs: ``` Adding API token for