feat: committing changes to dvc

MBenediktF · Sep 2, 2024 · 91d8648 · 91d8648
1 parent eb9086f
commit 91d8648
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 5 deletions.
diff --git a/Makefile b/Makefile
@@ -43,9 +43,10 @@ dvc_config_s3_access:
 	@dvc remote modify --local s3 access_key_id $(AWS_ACCESS_KEY_ID)
 	@dvc remote modify --local s3 secret_access_key $(AWS_SECRET_ACCESS_KEY)
 
-dvc_push_s3: dvc_config_s3_access
-	@dvc push -r s3	
-
-dvc_pull_s3: dvc_config_s3_access
+dvc_pull_s3: 
 	@dvc pull -r s3
 
+dvc_commit_push_s3: dvc_config_s3_access
+	@dvc commit datasets
+	@dvc push -r s3	
+
diff --git a/readme.md b/readme.md
@@ -17,7 +17,7 @@
 
 - Datasets are stored in the folder datasets. THe version control is handled by dvc. The datasets will be synced to github, but stored at another remote (default: s3)
 - To download the dataset files, run `make dvc_pull_s3`
-- To upload a new dataset, run `dvc add datasets/<filename>.zip` and `make dvc_push_s3`
+- To upload a new dataset file or sync changes, run `make dvc_comit_push_s3` and commit changes to github
 
 ## How to deploy a model