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

followup

Browse source
This commit is contained in:
Joey Hess 2020-05-11 13:06:39 -04:00
parent 3b15145703
commit 57451bd9a1
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
2 changed files with 25 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
doc/forum/backblaze_s3/comment_3_55362a91c4592775994999a843e648dc._comment Normal file
View file

@ -0,0 +1,9 @@
[[!comment format=mdwn
username="joey"
subject="""comment 3"""
date="2020-05-11T17:04:08Z"
content="""
Thanks for verifying it works. I've updated [[tips/using_Backblaze_B2]] to
mention this alternative, hopefully I got the config right. (Is the
endpoint always the same?)
"""]]

17
doc/tips/using_Backblaze_B2.mdwn
View file

@ -1,8 +1,23 @@
For using Backblaze B2 as a special remote, there are currently two
For using Backblaze B2 as a special remote, there are currently three
choices:
* Using [[special_remotes/rclone]]
(Actively maintained)
* Google Cloud Storage supports supports the same API as Amazon S3, so
git-annex's built-in [[S3 special remote|special_remotes/S3]] can be used
with it.
However, it needs S3 version 4 signatures, which are only supported by
git-annex 8.20200508 and newer.
Here is how to set up the special remote:
git annex initremote backblaze type=S3 signature=v4 host=$endpoint bucket=$bucketid protocol=https
Remember to replace $endpoint with the actual backblaze endpoint and $bucketid with
the bucketid.
* A dedicated special remote, <https://github.com/encryptio/git-annex-remote-b2>
(Last updated 2016)