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

followup; correct misleading comment

Browse source
This commit is contained in:
Joey Hess 2019-09-05 11:31:56 -04:00
parent c99526dd41
commit e11c324605
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
2 changed files with 14 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

13
doc/forum/Using_hashdirlower_layout_for_S3_special_remote/comment_2_9f22f7f14fab759caa1ddecda435311c._comment Normal file
View file

@ -0,0 +1,13 @@
[[!comment format=mdwn
username="joey"
subject="""comment 2"""
date="2019-09-05T15:29:57Z"
content="""
That comment was just bad wording or possibly I conflated S3 with how other
remotes that do use hash directories work. I've corrected the comment.
According to Amazon's documentation, S3 does not have a concept of
directories; "foo/bar" and "foo_bar" and "foo\\bar" are all just opaque
strings as far as it's concerned. So I don't see any point in using hash
directories with S3.
"""]]

2
doc/special_remotes/S3/comment_8_0fa68d584ee7f6b5c9058fba7e911a11._comment
View file

@ -4,7 +4,7 @@
subject="comment 8"
date="2013-01-20T20:37:09Z"
content="""
If encryption is not used, the files are stored in S3 as-is, and can be accessed directly. They are stored in a hashed directory structure with the names of their key used, rather than the original filename. To get back to the original filename, a copy of the git repo would also be needed.
If encryption is not used, the files are stored in S3 as-is, and can be accessed directly. The S3 bucket contains object named using the git-annex key, rather than the original filename. To get back to the original filename, a copy of the git repo would also be needed.
With encryption, you need the gpg key used in the encryption, or, for shared encryption, a symmetric key which is stored in the git repo.