Better JupyterHub Integration

[blink1073]

I propose that we have better integration with JupyterHub. In the short run, we add a flag to labhubapp that the front end uses to determine which connection loss dialog to show (cf #6399), and whether to add the commands/menu items that are currently provided by https://github.com/jupyterhub/jupyterlab-hub.

The next logical step would be to augment jupyterhub-singleuser to provide page_config_data and deprecate the use of labhubapp.

[blink1073]

cc @vidartf @ian-r-rose @yuvipanda

[blink1073]

cc @minrk

[yuvipanda]

Love it!

[blink1073]

👊

[blink1073]

cc @athornton

[jasongrout]

CC @vidartf

[athornton]

Very nice. Thumbs up. This in fact addresses a behavior related to reporting of kernel failure I was going to open an issue for once I had sufficient reproducibility. Plus it'd be nice to be able to get rid of labhub. (Also please feel free to cannibalize https://github.com/lsst-sqre/jupyterlab-savequit , which at our site, pretty much everyone uses rather than the Hub menu)

[blink1073]

Quick note to self: no changes are needed to jhub, we can just add the page config ourselves if the app has a hub_prefix property.

[vidartf]

I have ~0 experience with hub, so I have no idea what this issue is implying. What would the changes to jupyterlab itself be?

[blink1073]

We would update our extension to inject more page_config conditionally, and then add logic application-extension that runs in the presence of that page config.

[blink1073]

@athornton, thanks for the pointer! I'm wary of adding too much logic up front that might not be wanted in all contexts. I'd prefer to start small.

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related discussion.