Are you sure you want to delete this access key?
title | description |
---|---|
DagsHub Integration with DVC - Free ML Version Control Tool | DagsHub integration with DVC includes remote object storage, file diffing tracked by DVC, S3 compatibility, and Data Pipeline visualization for your ML projects. |
DVC{:rel="nofollow" target="_blank"} is an open-source version control tool for machine learning projects designed to handle large files, data sets, machine learning models, and metrics. It works on top of Git to easily integrate with your existing Git code repositories. DagsHub integration with DVC includes a fully configured remote object storage managed by DVC, showing and diffing DVC tracked files hosted on DagsHub Storage or S3 compatible, and Data Pipeline visualization.
DagsHub automatically configures a remote object storage for every repository with 100 GBs of free space. The storage can
be managed by DVC and easily configured with any machine. Using the DVC pointer files (.dvc
) and the dvc.lock
file,
host on the Git commit, DagsHub parsed the storage and displays the DVC tracked files under the Files tab.
Learn how to use DagsHub Storage
DagsHub supports visualizing and managing DVC data stored on any AWS S3, Google Cloud Storage, Azure Blob Storage, or any S3 Compatible storage including MinIO.
Learn how to configure your external bucket.
DagsHub parses the dvc.lock and dvc.yaml file to create the interactive data pipeline. The pipeline is versioned and holds valuable information about the different files, metrics, and data steps.
Enter a terminal in your project, paste the commands and run them
dvc remote add origin s3://dvc
dvc remote modify origin endpointurl https://dagshub.com/<DagsHub-user-name>/<repo_name>.s3
dvc remote modify origin --local access_key_id <Token>
dvc remote modify origin --local secret_access_key <Token>
??? info "Why --local?"
Everything you configure without --local
will end up in the .dvc/config
file, which is tracked by git, and appear in you repository.
Personal info like authentication details should always be kept local.
Note: You need to be inside a Git and DVC directory for this process to succeed. To learn how to do that, please follow the first part of the Get Started section.
dvc pull -r origin
dvc push -r origin
Press p or to see the previous file or, n or to see the next file
Are you sure you want to delete this access key?
Are you sure you want to delete this access key?
Are you sure you want to delete this access key?
Are you sure you want to delete this access key?