Index of files stored in git pointing to a remote storage. That sounds exactly like git LFS. Is there any significant difference? In particular in terms of backups.
Git LFS is 50k loc, this is 891 loc. There are other differences, but that is the main one.
I don't want a sophisticated backup system. I want one so simple that it disappears into the background.
I want to never fear data loss or my ability to restore with broken tools and a new computer while floating on a raft down a river during a thunder storm. This is what we train for.
Support for S3 means you can just have minio server somewhere acting as backup storage (and minio is pretty easy to replicate). I have local S3 on my NAS replicated to cheapo OVH serwer for backup
ajb|8 months ago
nathants|8 months ago
Too|8 months ago
nathants|8 months ago
Git LFS is 50k loc, this is 891 loc. There are other differences, but that is the main one.
I don't want a sophisticated backup system. I want one so simple that it disappears into the background.
I want to never fear data loss or my ability to restore with broken tools and a new computer while floating on a raft down a river during a thunder storm. This is what we train for.
orsorna|8 months ago
I don't see what value this provides that rsync, tar and `aws s3 cp` (or AWS SDK equivalent) provides.
nathants|8 months ago
yread|8 months ago
seized|8 months ago
Google Cloud Store Archive Tier is a tiny bit more.
nathants|8 months ago
My low value backups go into a cheap usb hdd from Best Buy.
1. https://github.com/nathants/mirror
PunchyHamster|8 months ago