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

Workspaces importer and exporter should be able to set the workspace name #5694

Closed
ian-r-rose opened this issue Nov 28, 2018 · 0 comments · Fixed by #5695
Closed

Workspaces importer and exporter should be able to set the workspace name #5694

ian-r-rose opened this issue Nov 28, 2018 · 0 comments · Fixed by #5695

Comments

@ian-r-rose
Copy link
Member

@ian-r-rose ian-r-rose commented Nov 28, 2018

Currently the workspaces importer checks that the workspace name is valid, and this check is pretty strict. In a JupyterHub environment this means that the workspace id must include the jupyterhub user name, which automatically makes workspace files less portable between different users. This makes distribution of workspaces more challenging for administrators. For an example, see this binder start script:

https://github.com/dask/dask-examples/blob/0c39b1c6348e118594397e8b61eec594ef011db1/binder/start#L6

It would be nice if the importer and exporter could take a --name argument that automatically overwrote the workspace id with the correct one (e.g., user/${USER_NAME}/${WORKSPACE_NAME}).

@ian-r-rose ian-r-rose transferred this issue from jupyterlab/jupyterlab_server Nov 28, 2018
@ian-r-rose ian-r-rose added this to the Future milestone Nov 28, 2018
@Zsailer Zsailer self-assigned this Nov 28, 2018
@lock lock bot locked as resolved and limited conversation to collaborators Aug 8, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

2 participants