Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: Compatibility with Cloudflare R2 #40

Open
WillMontgomery opened this issue Dec 3, 2022 · 4 comments
Open

Feature Request: Compatibility with Cloudflare R2 #40

WillMontgomery opened this issue Dec 3, 2022 · 4 comments
Labels
enhancement New feature or request help wanted Extra attention is needed

Comments

@WillMontgomery
Copy link

Cloudflare R2 is a great object storage platform and utilizes the same S3 API. Would be great to see this functionality added!

@qoomon
Copy link
Owner

qoomon commented Dec 3, 2022

What's hindering you from using ist right now if the cloudflare api is compatible with S3 api?

@qoomon
Copy link
Owner

qoomon commented Dec 3, 2022

Anyway do you have a url to a public accessible cloudflare storage so I could try it out and fix occurring problems.

@WillMontgomery
Copy link
Author

Hey there! Thanks for your fast response. The format used to access Cloudflare R2 buckets is using an access key ID and a secret access key, in addition to entering the API endpoint for that particular bucket. It appears this repo only supports unauthenticated viewing of publicly accessible buckets. To answer your question about a test bucket, R2 buckets are free up to 10GB here: https://www.cloudflare.com/products/r2/

@qoomon
Copy link
Owner

qoomon commented Dec 6, 2022

I don't have the time to implement authentication, sorry.

@qoomon qoomon added help wanted Extra attention is needed enhancement New feature or request labels Dec 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants