sharing folders via vsc groups #507
Conversation
| Sharing files and folders with other VSC users | ||
| ---------------------------------------------- | ||
|
|
||
| VSC users can share files/folders with other VSC users only via :ref:`VSC groups <vsc_groups>`. |
There was a problem hiding this comment.
In case ACLs are enabled it is possible to share data without having to use VSC groups.
| # change group name recursively below the top hierarchy you want to share | ||
| chgrp -R lp_shared_data $VSC_DATA/results/post-processed | ||
|
|
||
| - Make sure that the shared directory has read and execute access to all folders underneat, |
There was a problem hiding this comment.
This phrase is not very clear. I guess you mean that, in this example, $VSC_DATA and $VSC_DATA/results need to be readable and executable by the group lp_shared_data?
|
|
||
| VSC users can share files/folders with other VSC users only via :ref:`VSC groups <vsc_groups>`. | ||
| Imagine a VSC user who wants to share his post-processed data stored below the | ||
| ``$VSC_DATA/results/post-processed`` folder with another VSC user(s). |
There was a problem hiding this comment.
I understand that your additions deal with the technical aspect of sharing data, but the current example might be interpreted as advising users to share data through their $VSC_DATA directory. So I think at least a pointer to different storage options should be provided that indicates the ones more suited for sharing data (if this information is already available somewhere).
| chgrp lp_shared_data $VSC_DATA | ||
| chgrp lp_shared_data $VSC_DATA/results | ||
| # change group name recursively below the top hierarchy you want to share | ||
| chgrp -R lp_shared_data $VSC_DATA/results/post-processed |
There was a problem hiding this comment.
Referring to the setgid bit mentioned above can be useful here.
| :: | ||
|
|
||
| chmod -R g+r $VSC_DATA/results/post-processed | ||
| find $VSC_DATA/results/post-processed -type d -exec chmod g+x {} + |
There was a problem hiding this comment.
Maybe a stupid comment, but at some point it might be useful to mention that other users need to have the full path to the $VSC_DATA subdirectory that is being shared.
No description provided.