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 suggest we work towards a feature to allow user managed JupyterHub groups via /hub/admin#/groups determine configuration for user servers. And further, that we do it in a way based on JupyterHub's own concepts of groups to avoid implementing this to be specific to a certain identity provider, such as GitHub.
If we do this, we could for example let users of certain groups get certain shared folders mounted in read/write.
[...] understand if there are ways to make storage folders only visible and writable by certain GitHub teams and if this is the use model we want to adopt for some of the more resource intensive events we support.
I suggest we work towards a feature to allow user managed JupyterHub groups via
/hub/admin#/groups
determine configuration for user servers. And further, that we do it in a way based on JupyterHub's own concepts of groups to avoid implementing this to be specific to a certain identity provider, such as GitHub.If we do this, we could for example let users of certain groups get certain shared folders mounted in read/write.
Background
FreshDesk ticket from
nasa-cryo
at hub.cryointhecloud.comFreshDesk ticket from
victor
at victor.2i2c.cloudAction points
The text was updated successfully, but these errors were encountered: