DVC remotes are distributed storage locations for your data sets and ML models (similar to Git remotes, but for cached assets). This optional feature is typically used to share or back up copies of all or some of your data. Several types are supported: Amazon S3, Google Drive, SSH, HTTP, local file systems, among others.
Learn more about remote storage.
--help- prints the usage/help message, and exit.
--quiet- do not write anything to standard output. Exit with 0 if no problems arise, otherwise 1.
--verbose- displays detailed tracing information.
Learn more about local remotes.
We use the
--default) option of
dvc remote add for this:
$ dvc remote add -d myremote /path/to/remote
The project's config file should now look like this:
['remote "myremote"'] url = /path/to/remote [core] remote = myremote
$ dvc remote list myremote /path/to/remote newremote s3://mybucket/path
💡 Before adding an S3 remote, be sure to Create a Bucket.
$ dvc remote add newremote s3://mybucket/path $ dvc remote modify newremote endpointurl https://object-storage.example.com
The project's config file should now look something like this:
['remote "myremote"'] url = /path/to/remote [core] remote = myremote ['remote "newremote"'] url = s3://mybucket/path endpointurl = https://object-storage.example.com
dvc remote modify can't change the name of a DVC remote, but there's a
specific subcommand for this:
$ dvc remote rename oldremote newremote
$ dvc remote remove oldremote