Mirror/remotely-save
1
0
Fork 0
mirror of https://github.com/remotely-save/remotely-save.git synced 2024-06-07 21:10:45 +00:00
Code Issues Packages Projects Releases Wiki Activity
a084ec7728
remotely-save/docs/remote_services/s3_cloudflare_r2
History
fyears af71758ef7 add cloudflare r2
2024-01-03 00:08:51 +08:00
..
README.md add cloudflare r2 2024-01-03 00:08:51 +08:00
s3_cloudflare_r2_create_api_token.png add cloudflare r2 2024-01-03 00:08:51 +08:00
s3_cloudflare_r2_create_bucket.png add cloudflare r2 2024-01-03 00:08:51 +08:00
s3_cloudflare_r2_rs_settings.png add cloudflare r2 2024-01-03 00:08:51 +08:00

README.md

Cloudflare R2

Links

https://www.cloudflare.com/developer-platform/r2/

Steps

  1. Be aware that it may cost you money.

  2. Create a Cloudflare account and enable R2 feature. Credit card info might be required by Cloudflare, though Cloudflare provides generous free tier and zero egress fee.

  3. Create a bucket.

  4. Create an Access Key with "Object Read & Write" permission, and add specify to your created bucket. During the creation, you will also get the auto-generated secret key, and the endpoint address.

  5. In remotely-save setting page, input the address / bucket / access key / secret key. Region being set to us-east-1 is sufficient. Enable "Bypass CORS", because usually that's what you want.

    Click "check connectivity". (If you encounter an issue and sure the info are correct, please upgrade remotely-save to version >= 0.3.29 and try again.)

  6. Sync!

And Issue Related To "Check Connectivity"

If you encounter an issue and sure the info are correct, please upgrade remotely-save to version >= 0.3.29 and try again.

Cloudflare doesn't allow HeadBucket for access keys with "Object Read & Write". So it may be possible that checking connectivity is not ok but actual syncing is ok. New version >= 0.3.29 of the plugin fix this problem by using ListObjects instead of HeadBucket.