VDV - Void Data Versioning #119

Open
opened 2024-11-10 18:11:53 +02:00 by max · 0 comments
Owner

This is supposed to be a replacement for DVC, reimplementing only the functionality we actually use from it.

  • meant to be used with Git repos, so will integrate with Git
  • *.dvc -> *.vdv, file format should remain identical, but could be changed if deemed useful
  • simple config file in repo to determine where to store assets, as in DVC
  • maybe we can dynamically create S3 keys for client auth?
This is supposed to be a replacement for DVC, reimplementing only the functionality we actually use from it. - meant to be used with Git repos, so will integrate with Git - `*.dvc` -> `*.vdv`, file format should remain identical, but could be changed if deemed useful - simple config file in repo to determine where to store assets, as in DVC - maybe we can dynamically create S3 keys for client auth?
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: privatevoid.net/depot#119
No description provided.