So we’re experimenting on using S3 for uploads. S3 is quite slow for, well anything really, so wanted to put a CDN like Cloudfront in-front of it. The setting :s3_cdn_url seems to be ideal for that. Using it is not quite what I expected though, so wanted help to check my understanding.
I can understand that it doesn’t change older posts without rebaking, but since enabling we see this on new posts:
So, the actual optimized/thumb is shown in straight Slow S3, but the full inside the lightbox is Cloudfront? Is that right, as it would seem that CloudFront could be used in-front of S3 all the time for images?
I guess the other way to go would be to map a custom DNS entry to the S3 bucket and let something like Cloudflare alias it? Anyone have experience with this?
EDIT: Hmm, can’t use s3 virtual hosting domains with Discourse as it doesn’t like the periods in the bucket name then. It makes setting up like this not possible:
…which then stops simple DNS Cloudflare (as in not even using Cloudfront) improvements, as we can’t have a files.ourforum.com like mapping? Seems a bit of shame or maybe I am missing something?
EDIT2: Wildcard certs fault, ignore the edit bit if that helps.
Yep, I understand how SSL wild card certificates and periods work (or don’t work), but my question was more why the discourse S3 CDN setting wasn’t being used for the baked optimize image as well as the click-through.
When an image has a lightbox built when cooking a post, it seems that the non CDN URL is used, since when an image is ok to display without lightbox then the CDN is used. If anything it would be better the other way around, as in the multiple images in posts in the main topic is exactly the thing that would benefit from the CDN.
If my understanding of the feature is correct then I can try to figure out a pull request fix, but if it’s not then I need someone on the Discourse team like @codinghorror to take a look and let me know where I misunderstand the intention of this bit. Cheers!
