File: using_Backblaze_B2.mdwn

package info (click to toggle)
git-annex 10.20230126-3
  • links: PTS, VCS
  • area: main
  • in suites: bookworm
  • size: 69,344 kB
  • sloc: haskell: 74,654; javascript: 9,103; sh: 1,304; makefile: 203; perl: 136; ansic: 44
file content (25 lines) | stat: -rw-r--r-- 879 bytes parent folder | download | duplicates (4)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
For using Backblaze B2 as a special remote, there are currently three
choices:

* Using [[special_remotes/rclone]]  
  (Actively maintained)

* Backblaze B2 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)

At this time it's not clear which is better, so if you find one works
better than the other, please comment below.