mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

Added a comment: So where are the file stored?

Browse source
This commit is contained in:
git-annex.branchable.com@78dd096e15e9d37643bf695293cae77fec735698 2021-08-18 20:19:25 +00:00 committed by admin
parent ea675c4747
commit e23c24f0fa
1 changed files with 15 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

15
doc/how_it_works/comment_5_11e5141c9ffb37db4fa0c1bfb32c51a9._comment Normal file
View file

@ -0,0 +1,15 @@
[[!comment format=mdwn
username="git-annex.branchable.com@78dd096e15e9d37643bf695293cae77fec735698"
nickname="git-annex.branchable.com"
avatar="http://cdn.libravatar.org/avatar/f9a3a021d4457e45fb899b38ba0aed41"
subject="So where are the file stored?"
date="2021-08-18T20:19:25Z"
content="""
This is like a 1000ft overview, but doesn't actually say where the files are actually stored or how they're synchronized.
Does one need to setup a samba, sftp, or AWS bucket to contain the large files? Does a clone of the repo full down all of the large files, or just the files in the working directory that's checked out? Are files transferred via direct connection to other repos (ex the same SSH tunnel that git uses, http, etc) or is there a UDP p2p layer like syncthing or bittorrent that might struggle with certain NAT situations?
The sentence \"A file's content can be transferred from one repository to another by git-annex. Which repositories contain a given value is tracked by git-annex (see location tracking).\" makes it sound like the old versions of the large files only exist on computers that checked out those copies. Does this mean old versions of a file might be lost forever if a single clone is deleted and temporarily unavailable if clones that contain those revisions of the file are offline?
Is there a way to ensure that a clone has all copies of all of the files (for example, when using git with a central trusted server)?
"""]]