-
Notifications
You must be signed in to change notification settings - Fork 344
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.
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
Remove jupyterhub-configurator in 1.0.0? #901
Comments
I think I've come to see providing the jupyterhub-configurator in TLJH to configure default url specifically, as done now, seems like commiting to constructing and maintaing a car, teaching users how to drive it, and then suggesting they can use it to drive a few meters they could have walked with ease. With that analogy in mind, I suggest we don't try to help users drive it further and to a few new destinations, but instead help users be even more confident walkers able to get everywhere. @yuvipanda @GeorgianaElena @manics what do you think about this? Okay to remove the configurator? |
I've never used the configurator so I can't speak as to how useful it is. Since the docs say
Removing it is fine if you think that's best. |
I would also like it to be removed, but for a different reason - I think my initial approach is a technological dead end. Architectural poor choices were made that came to light as we used it in production. See 2i2c-org/features#26 for more details. I know that @GeorgianaElena spent a bunch of time integrating it into TLJH though, so would want to hear what she thinks too. |
I'd like to propose we remove the opt-in setup of jupyterhub-configurator.
Overview
According to the docs, the configurator is disabled by default but is documented as something that can be experimetnally enabled.
If it is enabled, the Spawner get's an imported ConfiguratorSpawnerMixin that checks the relevant configuration just in time.
the-littlest-jupyterhub/tljh/user_creating_spawner.py
Lines 41 to 50 in c6c3c96
What can be configured by the jupyterhub configurator is hardcoded in a tljh package bundled config file.
the-littlest-jupyterhub/tljh/configurer.py
Lines 278 to 304 in c6c3c96
That declares that the default url can be configured:
the-littlest-jupyterhub/tljh/jupyterhub_configurator_config.py
Line 1 in c6c3c96
Proposal motivations
default_url
?)tljh-config
or plain jupyterhub config.py
files to do ~anything without the configurator. Should we really teach jh admins another way of doing things just to configure default-url in a simpler way?tljh-config
is already a shortcut to configure things by adding another configuration layer, adding another with the configurator can make it harder to understand how things work overallThe text was updated successfully, but these errors were encountered: