- tls config is no longer allowed in static config file, add separate dynamic config
- no longer need to persist auth config ourselves (TraefikProxy handles this)
- make sure to reload proxy before reloading hub in tests
- Previously, we only printed warning and did not exit
- Split the warning over two lines rather than one
- -E is not required for tljh-config anymore (since it is in
/usr/bin, not /usr/local/bin), so do not ask users to use it.
https://github.com/jupyterhub/the-littlest-jupyterhub/pull/135
is the PR that made this change, and changed documentation in
most places.
workaround ruamel.yaml issue 255,
where once an empty dict or list has been written,
'flow' style is used thereafter, using dense `{key: value}` form
instead of traditional yaml block style.
instead of top-level files
- ensure directory is private
- both tljh and jupyterhub config go in there
- move old config.yaml to new location at install time
We do not want users to hand-edit YAML files. This has been a
major source of bugs and confusion for users in z2jh. Doing so
in a terminal text editor makes it even worse.
This lets users type commands directly to modify config.yaml file
rather than edit files directly. This makes it a lot less error
prone and user friendly.
Advanced users can still edit config.yaml manually.
Fixes#38
