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

Option for custom CDN endpoint when using S3 file store #448

Open
gmemstr opened this issue Jul 27, 2024 · 1 comment
Open

Option for custom CDN endpoint when using S3 file store #448

gmemstr opened this issue Jul 27, 2024 · 1 comment

Comments

@gmemstr
Copy link

gmemstr commented Jul 27, 2024

When using an S3 file store, it looks like files are fetched using a presigned URL direct from the bucket. This is probably okay for most people, but it would be nice to be able to define a custom CDN endpoint, for example if you want to put Cloudfront in front of the bucket with a custom URL or proxying a Cloudflare R2 bucket. This would let us stick with a single domain and configure caching to avoid excessive requests to the bucket.

I'm not familiar with Elixir, but I'm willing to give it a shot at implementing.

@ku1ik
Copy link
Contributor

ku1ik commented Aug 12, 2024

I actually thought about this too. Seems like a good idea.

We're serving files from a private bucket (i.e. objects themselves being private, requiring pre-signing). Do you have examples of how e.g. Cloudflare, Fastly, Cloudfront URLs would look like when compared to the original bucket URL? I assume simple domain substitution would only work for fully public objects, right?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants