-
Notifications
You must be signed in to change notification settings - Fork 0
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
How to customize a JupyterHub and BinderHub landing pages #31
Comments
Great question, @jmunroe! I think for our hubs' home page customization, in addition to the initcontainer, we have another container that 'syncs' changes every 5-10 minutes. That's missing here, and I'll add that today. |
In the meantime, deleting the pod should trigger a rescync. That can be done with:
|
Thanks! I've made an initial pass at applying 2i2c-branding to the landing page. Some of the "skills" required in customizing a landing page for Binderhub/JupyterHub:
Web dev can be "easy" if all of the tooling is already set up but can be daunting for the newcomer. Example: the binderhub template references a Customization of landing pages (for either JupyterHub and BinderHub) could be something that our communities can be empowered to do. Future action: develop sufficient documentation to make this possible/reasonable. |
As a feature, this is tracked in https://2i2c.productboard.com/feature-board/7803674-product-ideas/features/26289139/detail |
For http://agu-binder.2i2c.cloud, we want a customized landing page. The configuration for that hub includes the following:
My expectation is that by pushing changes to https://github.com/2i2c-org/agu-binder-custom-templates that should cause a change to the landing page visible at http://agu-binder.2i2c.cloud.
I assume I need to do something with
deployer
to trigger the appropriate helm action so cause that the template repo to be cloned again so that this hub picks up the changes and visible at http://agu-binder.2i2c.cloud.Trying
causes a
helm upgrade
but apparently no change to http://agu-binder.2i2c.cloud. I assume this because there has been no change to the helm charts so nothing needs to be modified.
Question: how can can trigger helm to rebuild this pod so that the changes made in https://github.com/2i2c-org/agu-binder-custom-templates get picked up?
The text was updated successfully, but these errors were encountered: