You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I want to have users with custom username and password, which is a feature already achieved by this repo.
However, all users can only use the kernel as same as the one which launched jupyterhub instance, if they want to run with specific version libraries, they will have to ask admin to do that, even they already created such env in same machine.
If we launch jupyterhub without this plugin, and config as following:
Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! 🤗
If you haven't done so already, check out Jupyter's Code of Conduct. Also, please try to follow the issue template as it helps other other community members to contribute more effectively.
You can meet the other Jovyans by joining our Discourse forum. There is also an intro thread there where you can stop by and say Hi! 👋
Welcome to the Jupyter community! 🎉
scruel
changed the title
How to specify user environment path for users to use their own kernels? (bin folder)
Ability to set user environment path (bin folder) for users to use their own kernels
Nov 9, 2022
Proposed change
I want to have users with custom username and password, which is a feature already achieved by this repo.
However, all users can only use the kernel as same as the one which launched jupyterhub instance, if they want to run with specific version libraries, they will have to ask admin to do that, even they already created such env in same machine.
If we launch jupyterhub without this plugin, and config as following:
Then for users, they can set
PATH
in~/.profile
to specify their own conda location:Then they can use jupyterhub with their own envs.
Or, might we can bind local users to jupyterhub users, then can just do samething?
The text was updated successfully, but these errors were encountered: