-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Support for CloudFront or other CDN #505
Comments
Hadn't thought about this. Will consider adding an optional |
This feature is already merged and will be available in the upcoming release this week. |
Yep, but in |
Sorry, I am a bit confused. Are you running |
I'm using docker image: |
I just updated to v2.1.0, and from /reopen |
Please share a screenshot of your S3 settings UI. |
I'm using Google Cloud Storage interop with S3 API. Images are being saved correctly in the bucket. |
The public URL seems to be incorrect. It should be something like |
No, I use my own CDN that uses the same domain for multiple buckets. |
Is your feature request related to a problem? Please describe.
listmonk already has support for uploading media into an S3 bucket. That's terrific. However, it is not always desirable to deliver content directly from the bucket itself. It is extremely common to put a CDN, usually AWS CloudFront, in front of the S3 bucket to handle the actual content delivery. Uploads still go to the S3 bucket, but the URLs in the emails would point at the CloudFront URL.
Describe the solution you'd like
Allow configuration of a CloudFront/CDN URL from which media uploaded to S3 will be delivered. When rendering emails, construct URLs pointing at the CDN host instead of at the S3 bucket directly.
The text was updated successfully, but these errors were encountered: