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

Browse source
This commit is contained in:
branch 2023-07-29 21:35:16 +00:00 • committed by admin
parent 02c5f1e3a8
commit 03a5f3ec6b
1 changed files with 7 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

7
doc/forum/Differences_between_unlocked_and_directory_remote.mdwn Normal file
View file

@ -0,0 +1,7 @@
As I am beginning to experiment with git-annex, I am trying to imagine a system as hand-free as possible, that could be usable even for non-git users once everything is setup. Knowing the safety limitations of using files directly, I tend towards using either an unlocked adjusted branch with annex.thin, or a directory special remote (exporttree=yes, importtree=yes), as git-annex will operate further away from the tracked data.
The setup will include multiple computers sharing the same tree, which will have multiple copies across other servers. As each computer will have a different set of prefered content rules, it is important to see missing files.
I feel that the unlocked mode is the safer option, but there is the appeal in having files mostly untouched as in the directory special remote.
How do both methods compare from a user perspective? What are their limitations? Is there a way to show hidden files on a directory special remote (as [drafted](https://git-annex.branchable.com/design/assistant/desymlink/))?