-
Notifications
You must be signed in to change notification settings - Fork 409
add cache.shared config reference and use case #971
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -37,6 +37,16 @@ to simply move it from an old cache location to the new one: | |
| $ mv .dvc/cache/* /path/to/dvc-cache | ||
| ``` | ||
|
|
||
| Now you need to ensure that cache files/directories have appropriate | ||
| permissions, so that they could be accessed by your collegues that are members | ||
| of the same group: | ||
|
|
||
| ```dvc | ||
| $ sudo find /path/to/dvc-cache -type f -exec chmod 0664 {} \; | ||
| $ sudo find /path/to/dvc-cache -type d -exec chmod 0775 {} \; | ||
| $ sudo chown -R myuser:ourgroup /path/to/dvc-cache/ | ||
|
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Needs clarification that the user needs to use his username and his group, that he shares with his team. Also |
||
| ``` | ||
|
|
||
| ## Configure shared cache | ||
|
|
||
| Tell DVC to use the directory we've set up above as an shared cache location by | ||
|
|
@@ -46,6 +56,13 @@ running: | |
| $ dvc config cache.dir /path/to/dvc-cache | ||
| ``` | ||
|
|
||
| And tell DVC to set group permissions on the newly created/downloaded cache | ||
| files: | ||
|
|
||
| ```dvc | ||
| $ dvc config cache.shared group | ||
| ``` | ||
|
|
||
|
Comment on lines
+59
to
+65
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The reason why it wasn't needed before is that I've assumed that people will just create their files with proper group permissions and so our cache files won't need any changes. That was clearly too much to ask, so we now do it explicitly. |
||
| Commit changes to `.dvc/config` and push them to your git remote: | ||
|
|
||
| ```dvc | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is presenting permissions in such way clear enough? I'm not sure if it is too hard to understand, maybe we are better describing it with words to make it as friendly as possible?