diff options
| author |  emanuele.ruffaldi@56b9c9a5c1f873994b869248e9b53aa20f437d20 <emanueleruffaldi@web> | 2016-01-12 00:32:31 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2016-01-12 00:32:31 +0000 |
| commit | bcceb66dfa9c56fcc815d3810e818068c8fce506 (patch) | |
| tree | d7afe7853c6404754b774bc9e3d254375e78021c | |
| parent | c940c1702a27f4644ecf03177d3adec03703a8ad (diff) | |
| -rw-r--r-- | doc/tips/Accessing_files_in_bare_remotes_without_git-annex.mdwn | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/doc/tips/Accessing_files_in_bare_remotes_without_git-annex.mdwn b/doc/tips/Accessing_files_in_bare_remotes_without_git-annex.mdwn new file mode 100644 index 000000000..c9af79cdf --- /dev/null +++ b/doc/tips/Accessing_files_in_bare_remotes_without_git-annex.mdwn @@ -0,0 +1,8 @@ + +git-annex is amazing for my large files backup necessities, but I am a bit scared for the long-term possibility of accessing data, without git-annex. + +For this reason I have prepared a small Python tool that accesses the content of bare git-annex repositories. The tool retrieves the locations of a file, and the path to the file in the current annex. This works with the last v6 version of the git-annex format. + +This is motivated by the fact that in the master branch the files are stores as links to .git/annex/objects/XX/YY/KEY/KEY (as it is correct for non-bare repos), while in the bare the files are stored in annex/objecst/ZZ/WW/KEY/KEY. + +The source code is available here: <https://gist.github.com/eruffaldi/924f6b53a63dede6e59f> |