From 6edb1e1878718d87e4b4e385915a37415ac8fa7c Mon Sep 17 00:00:00 2001 From: Justin Tyberg Date: Fri, 6 May 2016 15:47:31 -0400 Subject: [PATCH] Update README to be more explicit about JHub TLS cert and key files. (c) Copyright IBM Corp. 2016 --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index d850d86..a3fc478 100644 --- a/README.md +++ b/README.md @@ -134,7 +134,7 @@ OAUTH_CALLBACK_URL=https:///hub/oauth_callback Configure JupyterHub and build it into a Docker image. -1. Copy your TLS certificate and key to a directory named `secrets` within this repository directory. These will be added to the Docker image at build time. +1. Copy the TLS certificate chain and key files for the JupyterHub server to a directory named `secrets` within this repository directory. These will be added to the JupyterHub Docker image at build time. If you do not have a certificate chain and key, you can either [create self-signed versions](https://jupyter-notebook.readthedocs.org/en/latest/public_server.html#using-ssl-for-encrypted-communication), or obtain real ones from [Let's Encrypt](https://letsencrypt.org) (see the [letsencrypt example](examples/letsencrypt/README.md) for instructions). ``` mkdir -p secrets