Update doc

[nor...@perkeep.org]

https://github.com/perkeep/perkeep/commit/c48464f3ca2d9b23f9864576d5aa698ddb11c37a

commit c48464f3ca2d9b23f9864576d5aa698ddb11c37a
Author: kalidor <kal...@unixed.fr>
Date: Fri Mar 18 14:26:07 2022 +0100

Update doc

diff --git a/doc/server-config.md b/doc/server-config.md
index a106b06..c00b688 100644
--- a/doc/server-config.md
+++ b/doc/server-config.md
@@ -102,6 +102,8 @@ endpoint instead of AWS S3, such as `my-minio-server.example.com`. A specific
region may be specified by using [Low-level Configuration](#lowlevel), though
the bucket's region will generally be detected automatically.

+The `s3` storage option can be used for `b2` since it's possible to use AWS go SDK [backblaze article](https://help.backblaze.com/hc/en-us/articles/360047629713-Using-the-AWS-Go-SDK-with-B2). However since it requires the region to be provided, using [Low-level Configuration](#lowlevel) is preferred.
+
Additionally, there are two mutually exclusive options:

* `packRelated`: if true, blobs are automatically repacked for fast read access.
diff --git a/doc/storage-examples.md b/doc/storage-examples.md
index 1fee692..181876e 100644
--- a/doc/storage-examples.md
+++ b/doc/storage-examples.md
@@ -70,3 +70,20 @@ Finally, add the b2 config line to your perkeep `server-config.json`:
```
"b2": "keyID:applicationKey:bucket"
```
+
+It is also possible to use `s3` configuration to interact with `b2` API.
+
+This is an example of low-level configuration file:
+
+```json
+"/bs2/": {
+ "handler": "storage-s3",
+ "handlerArgs":{
+ "bucket":"<BUCKET>",
+ "aws_region":"us-west-004",
+ "aws_access_key":"<API_KEY>",
+ "aws_secret_access_key":"<APPLICATION_KEY>",
+ "hostname":"s3.us-west-004.backblazeb2.com"
+ }
+ }
+```
\ No newline at end of file