s3: add petabox.io to s3 providers
This commit is contained in:
Andrei Smirnov
GitHub
parent
31caa019fa
commit
f226f2dfb1
4 changed files with 216 additions and 4 deletions
|
|
@ -152,6 +152,7 @@ WebDAV or S3, that work out of the box.)
|
|||
{{< provider name="Oracle Object Storage" home="https://www.oracle.com/cloud/storage/object-storage" config="/oracleobjectstorage/" >}}
|
||||
{{< provider name="ownCloud" home="https://owncloud.org/" config="/webdav/#owncloud" >}}
|
||||
{{< provider name="pCloud" home="https://www.pcloud.com/" config="/pcloud/" >}}
|
||||
{{< provider name="Petabox" home="https://petabox.io/" config="/s3/#petabox" >}}
|
||||
{{< provider name="PikPak" home="https://mypikpak.com/" config="/pikpak/" >}}
|
||||
{{< provider name="premiumize.me" home="https://premiumize.me/" config="/premiumizeme/" >}}
|
||||
{{< provider name="put.io" home="https://put.io/" config="/putio/" >}}
|
||||
|
|
|
|||
|
|
@ -24,6 +24,7 @@ The S3 backend can be used with a number of different providers:
|
|||
{{< provider name="IONOS Cloud" home="https://cloud.ionos.com/storage/object-storage" config="/s3/#ionos" >}}
|
||||
{{< provider name="Liara Object Storage" home="https://liara.ir/landing/object-storage" config="/s3/#liara-cloud" >}}
|
||||
{{< provider name="Minio" home="https://www.minio.io/" config="/s3/#minio" >}}
|
||||
{{< provider name="Petabox" home="https://petabox.io/" config="/s3/#petabox" >}}
|
||||
{{< provider name="Qiniu Cloud Object Storage (Kodo)" home="https://www.qiniu.com/en/products/kodo" config="/s3/#qiniu" >}}
|
||||
{{< provider name="RackCorp Object Storage" home="https://www.rackcorp.com/" config="/s3/#RackCorp" >}}
|
||||
{{< provider name="Scaleway" home="https://www.scaleway.com/en/object-storage/" config="/s3/#scaleway" >}}
|
||||
|
|
@ -5362,6 +5363,166 @@ For Netease NOS configure as per the configurator `rclone config`
|
|||
setting the provider `Netease`. This will automatically set
|
||||
`force_path_style = false` which is necessary for it to run properly.
|
||||
|
||||
### Petabox
|
||||
|
||||
Here is an example of making a [Petabox](https://petabox.io/)
|
||||
configuration. First run:
|
||||
|
||||
```bash
|
||||
rclone config
|
||||
```
|
||||
|
||||
This will guide you through an interactive setup process.
|
||||
|
||||
```
|
||||
No remotes found, make a new one?
|
||||
n) New remote
|
||||
s) Set configuration password
|
||||
n/s> n
|
||||
|
||||
Enter name for new remote.
|
||||
name> My Petabox Storage
|
||||
|
||||
Option Storage.
|
||||
Type of storage to configure.
|
||||
Choose a number from below, or type in your own value.
|
||||
[snip]
|
||||
XX / Amazon S3 Compliant Storage Providers including AWS, ...
|
||||
\ "s3"
|
||||
[snip]
|
||||
Storage> s3
|
||||
|
||||
Option provider.
|
||||
Choose your S3 provider.
|
||||
Choose a number from below, or type in your own value.
|
||||
Press Enter to leave empty.
|
||||
[snip]
|
||||
XX / Petabox Object Storage
|
||||
\ (Petabox)
|
||||
[snip]
|
||||
provider> Petabox
|
||||
|
||||
Option env_auth.
|
||||
Get AWS credentials from runtime (environment variables or EC2/ECS meta data if no env vars).
|
||||
Only applies if access_key_id and secret_access_key is blank.
|
||||
Choose a number from below, or type in your own boolean value (true or false).
|
||||
Press Enter for the default (false).
|
||||
1 / Enter AWS credentials in the next step.
|
||||
\ (false)
|
||||
2 / Get AWS credentials from the environment (env vars or IAM).
|
||||
\ (true)
|
||||
env_auth> 1
|
||||
|
||||
Option access_key_id.
|
||||
AWS Access Key ID.
|
||||
Leave blank for anonymous access or runtime credentials.
|
||||
Enter a value. Press Enter to leave empty.
|
||||
access_key_id> YOUR_ACCESS_KEY_ID
|
||||
|
||||
Option secret_access_key.
|
||||
AWS Secret Access Key (password).
|
||||
Leave blank for anonymous access or runtime credentials.
|
||||
Enter a value. Press Enter to leave empty.
|
||||
secret_access_key> YOUR_SECRET_ACCESS_KEY
|
||||
|
||||
Option region.
|
||||
Region where your bucket will be created and your data stored.
|
||||
Choose a number from below, or type in your own value.
|
||||
Press Enter to leave empty.
|
||||
1 / US East (N. Virginia)
|
||||
\ (us-east-1)
|
||||
2 / Europe (Frankfurt)
|
||||
\ (eu-central-1)
|
||||
3 / Asia Pacific (Singapore)
|
||||
\ (ap-southeast-1)
|
||||
4 / Middle East (Bahrain)
|
||||
\ (me-south-1)
|
||||
5 / South America (São Paulo)
|
||||
\ (sa-east-1)
|
||||
region> 1
|
||||
|
||||
Option endpoint.
|
||||
Endpoint for Petabox S3 Object Storage.
|
||||
Specify the endpoint from the same region.
|
||||
Choose a number from below, or type in your own value.
|
||||
1 / US East (N. Virginia)
|
||||
\ (s3.petabox.io)
|
||||
2 / US East (N. Virginia)
|
||||
\ (s3.us-east-1.petabox.io)
|
||||
3 / Europe (Frankfurt)
|
||||
\ (s3.eu-central-1.petabox.io)
|
||||
4 / Asia Pacific (Singapore)
|
||||
\ (s3.ap-southeast-1.petabox.io)
|
||||
5 / Middle East (Bahrain)
|
||||
\ (s3.me-south-1.petabox.io)
|
||||
6 / South America (São Paulo)
|
||||
\ (s3.sa-east-1.petabox.io)
|
||||
endpoint> 1
|
||||
|
||||
Option acl.
|
||||
Canned ACL used when creating buckets and storing or copying objects.
|
||||
This ACL is used for creating objects and if bucket_acl isn't set, for creating buckets too.
|
||||
For more info visit https://docs.aws.amazon.com/AmazonS3/latest/dev/acl-overview.html#canned-acl
|
||||
Note that this ACL is applied when server-side copying objects as S3
|
||||
doesn't copy the ACL from the source but rather writes a fresh one.
|
||||
If the acl is an empty string then no X-Amz-Acl: header is added and
|
||||
the default (private) will be used.
|
||||
Choose a number from below, or type in your own value.
|
||||
Press Enter to leave empty.
|
||||
/ Owner gets FULL_CONTROL.
|
||||
1 | No one else has access rights (default).
|
||||
\ (private)
|
||||
/ Owner gets FULL_CONTROL.
|
||||
2 | The AllUsers group gets READ access.
|
||||
\ (public-read)
|
||||
/ Owner gets FULL_CONTROL.
|
||||
3 | The AllUsers group gets READ and WRITE access.
|
||||
| Granting this on a bucket is generally not recommended.
|
||||
\ (public-read-write)
|
||||
/ Owner gets FULL_CONTROL.
|
||||
4 | The AuthenticatedUsers group gets READ access.
|
||||
\ (authenticated-read)
|
||||
/ Object owner gets FULL_CONTROL.
|
||||
5 | Bucket owner gets READ access.
|
||||
| If you specify this canned ACL when creating a bucket, Amazon S3 ignores it.
|
||||
\ (bucket-owner-read)
|
||||
/ Both the object owner and the bucket owner get FULL_CONTROL over the object.
|
||||
6 | If you specify this canned ACL when creating a bucket, Amazon S3 ignores it.
|
||||
\ (bucket-owner-full-control)
|
||||
acl> 1
|
||||
|
||||
Edit advanced config?
|
||||
y) Yes
|
||||
n) No (default)
|
||||
y/n> No
|
||||
|
||||
Configuration complete.
|
||||
Options:
|
||||
- type: s3
|
||||
- provider: Petabox
|
||||
- access_key_id: YOUR_ACCESS_KEY_ID
|
||||
- secret_access_key: YOUR_SECRET_ACCESS_KEY
|
||||
- region: us-east-1
|
||||
- endpoint: s3.petabox.io
|
||||
Keep this "My Petabox Storage" remote?
|
||||
y) Yes this is OK (default)
|
||||
e) Edit this remote
|
||||
d) Delete this remote
|
||||
y/e/d> y
|
||||
```
|
||||
|
||||
This will leave the config file looking like this.
|
||||
|
||||
```
|
||||
[My Petabox Storage]
|
||||
type = s3
|
||||
provider = Petabox
|
||||
access_key_id = YOUR_ACCESS_KEY_ID
|
||||
secret_access_key = YOUR_SECRET_ACCESS_KEY
|
||||
region = us-east-1
|
||||
endpoint = s3.petabox.io
|
||||
```
|
||||
|
||||
### Storj
|
||||
|
||||
Storj is a decentralized cloud storage which can be used through its
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue