Skip to content
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

[ENH] - Eliminate the jhub-native-proxy requirement #519

Open
mcg1969 opened this issue Nov 11, 2024 · 0 comments
Open

[ENH] - Eliminate the jhub-native-proxy requirement #519

mcg1969 opened this issue Nov 11, 2024 · 0 comments

Comments

@mcg1969
Copy link

mcg1969 commented Nov 11, 2024

Feature description

I would like to propose that work be done to eliminate the need for jhub-native-proxy to be installed in the application environment.

Consider the standard JupyterHub session for a moment. Thanks to nb_conda_kernels, the kernel environments where notebooks are run do not need to be the same as the JupyterLab environment responsible for rendering the JupyterLab UI. This separation is beneficial not just because it allows us to leverage multiple environments in a single JupyterLab session. But it also ensures that JupyterLab's dependencies don't conflict with the dependencies in the kernel environment. The packages like ipykernel and r-irkernel are far more lightweight in that regard.

For application, jhub-native-proxy sits in the position of JupyterLab, and the application code sits in the position of the kernel environment. jhub-apps should at least optionally allow these two environments to be separate.

Value and/or benefit

For me, the most important benefit of this improvement is that it will make it easier to port applications from other data science environments.

Anything else?

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant