-
-
Notifications
You must be signed in to change notification settings - Fork 866
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[docs] add instructions to use S3 backend with Backblaze B2 (#1105)
Co-authored-by: Pat Patterson <[email protected]>
- Loading branch information
Showing
1 changed file
with
13 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,13 @@ | ||
Backblaze B2 | ||
============ | ||
|
||
Backblaze B2 implements an `S3 Compatible API <https://www.backblaze.com/b2/docs/s3_compatible_api.html>`_. To use it as a django-storages backend: | ||
|
||
#. Sign up for a `Backblaze B2 account <https://www.backblaze.com/b2/sign-up.html?referrer=nopref>`_, if you have not already done so. | ||
#. Create a public or private bucket. Note that object-level ACLs are not supported by B2 - all objects inherit their bucket's ACLs. | ||
#. Create an `application key <https://www.backblaze.com/b2/docs/application_keys.html>`_. Best practice is to limit access to the bucket you just created. | ||
#. Follow the instructions in the :doc:`Amazon S3 docs <amazon-S3>` with the following exceptions: | ||
|
||
* Set ``AWS_S3_REGION_NAME`` to your Backblaze B2 region, for example, ``us-west-004`` | ||
* Set ``AWS_S3_ENDPOINT_URL`` to ``https://s3.${AWS_S3_REGION_NAME}.backblazeb2.com`` | ||
* Set the values of ``AWS_ACCESS_KEY_ID`` and ``AWS_SECRET_ACCESS_KEY`` to the application key id and application key you created in step 2. |