doc[Configure Remote Storage]: The remote configure should have type prefix

Xiangxuan Qu 2023-05-24 23:25:51 +09:00
parent b6a064a736
commit 0a909e5ec0

@ -2,7 +2,7 @@
Here are a list of vendors supported. For other S3 compatible vendors, you can use just s3, but usually you may need to tweak these parameters:
```
remote.configure -name=cloud1 -type=s3 -access_key=xxx -secret_key=yyy -s3.endpoint=zzzzz -s3.force_path_style=true -s3.v4_signature=false
remote.configure -name=cloud1 -type=s3 -s3.access_key=xxx -s3.secret_key=yyy -s3.endpoint=zzzzz -s3.force_path_style=true -s3.v4_signature=false
```
| Name | Type | Note | Reference |
@ -31,7 +31,8 @@ Run `remote.configure` in `weed shell`:
remote.configure
# set or update a configuration
remote.configure -name=cloud1 -type=s3 -access_key=xxx -secret_key=yyy
# storage class default value is "STANDARD_IA"
remote.configure -name=cloud1 -type=s3 -s3.access_key=xxx -s3.secret_key=yyy -s3.storage_class="STANDARD"
remote.configure -name=cloud2 -type=gcs -gcs.appCredentialsFile=~/service-account-file.json
remote.configure -name=cloud3 -type=azure -azure.account_name=xxx -azure.account_key=yyy