TL;DR: Users should be able to create new files in Shared folders, but file permission must be matched to Shared folder. By default the file is created under the spawned user, resulting in other people not able to access these shared files.
Setup: Multiple-user access on a company server
- OS: Ubuntu 18.04.2 LTS
- Jupyter conda installation (
conda install -c conda-forge jupyterhub)
- jupyter_client 5.2.4 py37_0
- jupyter_core 4.4.0 py37_0
- jupyterhub 1.0.0 py37_0 conda-forge
- jupyterlab 1.1.4 pyhf63ae98_0
- jupyterlab_server 1.0.6 py_0
All of JupyterHub’s setup has been done with a system user called “miniconda” and everyone who can access the notebooks are part of the group “miniconda”.
Since security is important, this “miniconda” user does not have
sudospawner is used by “miniconda” to start-up JupyterLab instances for other Ubuntu users. “miniconda” is added to group “shadow” for non-root PAM authentication.
To share certain notebooks, every “miniconda” group user has a folder
~/jupyterhub/code_share, which is symlinked to
sudo ln -s /etc/jupyterhub/code_share jupyterhub/code_share).
All works fine, but when a user clicks the ‘+’ button and creates a new file in the
code_share folder, this file should have permissions set as
miniconda:miniconda, but currently it is created with
I want at least the group to be automatically set to “miniconda”, but preferably both. Also with permission for read/write for both user and group. How do I do this?