Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Should be JUPYTERHUB_CRYPT_KEY #764

Merged
merged 2 commits into from
Jul 16, 2018
Merged

Should be JUPYTERHUB_CRYPT_KEY #764

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c743ce2
Should be JUPYTERHUB_CRYPT_KEY
elgalu Jul 15, 2018
438397a
schema.yaml wording
consideRatio Jul 15, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion jupyterhub/schema.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -266,7 +266,7 @@ properties:
auth_state will be encrypted and stored in the Hub’s database. This can include things like authentication tokens, etc. to be passed to Spawners as environment variables.
Encrypting auth_state requires the cryptography package.
It must contain one (or more, separated by ;) 32B encryption keys. These can be either base64 or hex-encoded.
The JUPYTERHUB_CRYPTO_KEY envirionment variable will be used to set this key.
The JUPYTERHUB_CRYPT_KEY environment variable for the hub pod is set using this entry.

This can be generated with `openssl rand -hex 32`.

Expand Down