Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
сlarify differences and use cases for external storage mechanisms? #566
I've noticed that in general the different mechanisms DVC has to handle external storage are confusing. This includes DVC remotes, external dependencies/outputs/cache, and
We have independent docs explaining each one but no single document (or consistent references throughout) so users can clearly identify which mechanism does what or solves which problem – In fact I wonder whether the same external data problem could be solved with one or another mechanism (which could add to the confusion).
Well, we do have this page https://dvc.org/doc/user-guide/external-outputs#description (and issue #143) that try to combine external outputs and external cache into a single doc but I think the effort should probably encompass all of these mechanisms.
I'm not sure exactly how to address this so just opening this possible issue and cc @iterative/engineering for a discussion. Thanks
changed the title
Clarify differences and use cases for external storage mechanisms?
Aug 20, 2019
@jorgeorpinel , I don't have any solution to this but I agree that having a page explaining how to deal with external storage would be helpful.
A good next step would be to have several questions that we want this page to answer.
What I've identified (from skimming Discord) is that there are a lot of questions related to remote configuration and usage. Currently, there's no single page to refer to for tips and tricks when setting up a remote. Users need to go through the
Another frequent question is about NFS / CIFS we have no entry about this in our docs (as you already noted in your comment)