CloudFlare R2 Buckets
I'm trying to work my way through configuring a cloudflare R2 bucket.
The instructions are pretty straightforward until you get to step #3, "Obtain R2 Endpoint."
If I follow what is saying here, you're using a Public Development URL, yet the CloudFlare docs recommend not using that if you want any access control.
They recommend using a custom domain, but I'm not following what is being asked:
- Is the requested domain a subdomain of the community domain?
- a completely different domain?
What should the "public URL" and "Endpoint URL" look like?
I had the same issue. The FC documentation needs to be updated to match what's actually showing on Cloudflare's side. With that said, what I did was just follow what the FC Doc's instructions say and forego (or don't follow what Cloudflare's warnings are), and it worked for me.
I did abide by the Cloudflare warning and it really screwed up the setup, so I had to delete everything and start over, and the second time I just followed the FC instructions all the way through. 😀
David Fore, so you're saying that despite the warnings, it works?
It's the "non-production use case" warning that worries me. I don't want to be caught in a situation where the media all of a sudden is not available. ...and yes, I can see that using the Public development URL is easier.
but...
- rate limited
- unsupported access path
- development purposes only
- no cache management
- no consistent reliability and performance
😱
Wesley Peace Yes. I just did this with my 3rd Community site yesterday evening, and it's all working good. But to answer your question concerning the specific "list" you gave, I'd have to refer to the devs on this as I didn't get too far in-depth with all of that.