-
Notifications
You must be signed in to change notification settings - Fork 67
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
[Platform Initiative] Roll out jupyterhub-fancy-profiles for all hubs #5054
Comments
I've been testing this on a bunch of different hubs today, and fixed a couple minor bugs that I discovered (along with @oliverroick). I will roll this out early in the morning tomorrow (thursday) and watch for support tickets if they come! |
I'm going to roll it out by hand, testing each hub as I go. I made a list of hubs this should go out to on the issue description |
Blog post at 2i2c-org/2i2c-org.github.io#338. I think once that's done, we can mark this initiative as completed. |
2i2c-org/2i2c-org.github.io#338 merged. I've also updated the Service Guide docs to reflect this change 2i2c-org/docs#247. Marking this as complete 🎉 |
The profile selection screen is what users see after they log in to the hub - so it's the 'logged in homepage' of the hub. Currently, most hubs use the standard profile screen that comes with kubespawner, so it looks like this:
As part of the GESIS grant, we created jupyterhub-fancy-profiles, a more modern (and backwards compatible) replacement for the profile selector. It looks like this:
It also allows for connecting to a binderhub backend to allow for dynamic image building on the fly, and is a pre-requisite for enabling 'build-your-own' image features.
We have rolled this out to a few well used hubs (primarily NASA VEDA) for a few months without issue. This initiative tracks rolling this out to all our communities
Backwards compatibility
jupyterhub-fancy-profiles
is designed to be fully backwards compatible with the existing upstream profiles work, so config change is needed.Hubs affected
Definition of done
jupyterhub-fancy-profiles
is rolled out to all existing hubsThe text was updated successfully, but these errors were encountered: