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

response

Browse source
This commit is contained in:
Joey Hess 2016-04-13 15:23:11 -04:00
parent 54942c818b
commit e462f9a34e
Failed to extract signature
1 changed files with 20 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

20
doc/special_remotes/S3/comment_23_b503ce70a4f008be580a069420361686._comment Normal file
View file

@ -0,0 +1,20 @@
[[!comment format=mdwn
username="joey"
subject="""comment 23"""
date="2016-04-13T19:13:35Z"
content="""
@tim, are the git-annex repositories going to be connected? If so,
`git-annex initremote` the S3 remote to one, merge it into the next
repo, and then `git annex enableremote` the S3 remote there.
That's the sane way. If you want for some reason to have multiple separate
git-annex repositories, that all try to use the same S3 bucket, without
knowing about one-another, I have to recommend against it. You're setting
yourself up to shoot yourself in the foot, and quite possibly lose data.
While you can `git annex enableremote` the same bucket repeatedly in the
different repositories, each time it will be given a different uuid, and
since the uuid is stored in the bucket, this will prevent `git annex
enableremote` from being used for the old uuid, since it will see the
bucket has a different uuid now.
"""]]