R2 caching
I am looking into building a plugin for Logseq that allows users to upload and view files from R2.
I am looking through https://github.com/kotx/render to get a better idea of how to setup file read.
in there readme there is the following note:
my project is meant to be used by different users. I do not want to set a specific domain. Users will be able to configure thier bucket, account, etc.. similar to other S3 storage tools but via the worker API instead of the S3 compatible API.
does this mean I can't take advantage of caching? should users configure thier own domain as well for private file viewing? seems unnecssary
I am looking through https://github.com/kotx/render to get a better idea of how to setup file read.
in there readme there is the following note:
Note: Due to how custom domains for workers work, you MUST use a route to take advantage of caching. Cloudflare may fix this soon. Also note that *.workers.dev domains do not cache responses. You MUST use a route to your own (sub)domain.
my project is meant to be used by different users. I do not want to set a specific domain. Users will be able to configure thier bucket, account, etc.. similar to other S3 storage tools but via the worker API instead of the S3 compatible API.
does this mean I can't take advantage of caching? should users configure thier own domain as well for private file viewing? seems unnecssary
GitHub
Cloudflare Worker to proxy and cache requests to R2 - GitHub - kotx/render: Cloudflare Worker to proxy and cache requests to R2
Welcome to the official Cloudflare Developers server. Here you can ask for help and stay updated with the latest news
85,042Members
Resources
Similar Threads
Was this page helpful?
