From 30fa305c074fccb44c7ef0130d08be1481b1aeca Mon Sep 17 00:00:00 2001 From: cuspat96 Date: Thu, 2 Aug 2018 21:29:29 +0200 Subject: [PATCH] Clarify B2 Application Keys once again This commit fixes documentation about Application Keys in Backblaze B2. --- doc/030_preparing_a_new_repo.rst | 7 +------ 1 file changed, 1 insertion(+), 6 deletions(-) diff --git a/doc/030_preparing_a_new_repo.rst b/doc/030_preparing_a_new_repo.rst index 21ffa4e0e..0131748ca 100644 --- a/doc/030_preparing_a_new_repo.rst +++ b/doc/030_preparing_a_new_repo.rst @@ -301,12 +301,7 @@ dashboard in on the "Buckets" page when signed into your B2 account: $ export B2_ACCOUNT_ID= $ export B2_ACCOUNT_KEY= -You can either specify the so-called "Master Application Key" here (which can -access any bucket at any path) or a dedicated "Application Key" created just -for restic (which may be restricted to a specific bucket and/or path). The -master key consists of a ``B2_ACCOUNT_ID`` and a ``B2_ACCOUNT_KEY``, and each -application key also is a pair of ``B2_ACCOUNT_ID`` and ``B2_ACCOUNT_KEY``. The -ID of an application key is much longer than the ID of the master key. +.. note:: In case you want to use Backblaze Application Keys replace and with and respectively. 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