Merge pull request #2368 from rlue/doc/backblaze

Clarify docs for Backblaze B2 support
This commit is contained in:
rawtaz 2019-11-22 11:10:22 +01:00 committed by GitHub
commit 3d4f2dd6b4
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23

View file

@ -329,9 +329,9 @@ dashboard on the "Buckets" page when signed into your B2 account:
.. code-block:: console
$ export B2_ACCOUNT_ID=<MY_APPLICATION_KEY_ID>
$ export B2_ACCOUNT_KEY=<MY_SECRET_ACCOUNT_KEY>
$ export B2_ACCOUNT_KEY=<MY_APPLICATION_KEY>
.. note:: In case you want to use Backblaze Application Keys replace <MY_APPLICATION_KEY_ID> and <MY_SECRET_ACCOUNT_KEY> with <applicationKeyId> and <applicationKey> respectively.
.. note:: As of version 0.9.2, restic supports both master and non-master `application keys <https://www.backblaze.com/b2/docs/application_keys.html>`__. If using a non-master application key, ensure that it is created with at least **read and write** access to the B2 bucket. On earlier versions of restic, a master application key is required.
You can then initialize a repository stored at Backblaze B2. If the
bucket does not exist yet and the credentials you passed to restic have the