Comments on: Using Amazon’s CloudFront with Rails & Paperclip http://blog.tristanmedia.com/2009/09/using-amazons-cloudfront-with-rails-and-paperclip/ One can never have enough scripting languages: Notes on Perl, PHP, and Ruby Wed, 18 Aug 2010 19:38:44 +0000 hourly 1 http://wordpress.org/?v=3.0 By: Barry http://blog.tristanmedia.com/2009/09/using-amazons-cloudfront-with-rails-and-paperclip/comment-page-1/#comment-181 Barry Tue, 13 Apr 2010 21:32:49 +0000 http://blog.tristanmedia.com/?p=56#comment-181 Mike, I find just using the CDN is fast enough, and I want people's browsers to cache all of my assets. Your approach means they might get a different URL for an asset every time they visit one of my pages, so that I end up paying more for outgoing bandwidth. Mike, I find just using the CDN is fast enough, and I want people's browsers to cache all of my assets. Your approach means they might get a different URL for an asset every time they visit one of my pages, so that I end up paying more for outgoing bandwidth.

]]> By: Mike Larkin http://blog.tristanmedia.com/2009/09/using-amazons-cloudfront-with-rails-and-paperclip/comment-page-1/#comment-180 Mike Larkin Tue, 13 Apr 2010 19:54:02 +0000 http://blog.tristanmedia.com/?p=56#comment-180 Excellent write up! One thing I'd suggest would be to use multiple CNAMEs to serve assets -- most browsers limit simultaneous connections to a subdomain to a max of 2, so if you use something like cnd0, cdn1, cdn2, cdn3, you can speed things up a bit: :s3_host_alias => "cdn#{rand(4)}.pixellent.com" Excellent write up! One thing I'd suggest would be to use multiple CNAMEs to serve assets -- most browsers limit simultaneous connections to a subdomain to a max of 2, so if you use something like cnd0, cdn1, cdn2, cdn3, you can speed things up a bit:

:s3_host_alias => "cdn#{rand(4)}.pixellent.com"

]]> By: Barry http://blog.tristanmedia.com/2009/09/using-amazons-cloudfront-with-rails-and-paperclip/comment-page-1/#comment-111 Barry Fri, 29 Jan 2010 18:13:52 +0000 http://blog.tristanmedia.com/?p=56#comment-111 Hello, Cameron. It doesn't work that way. The interpolation is using attachment.instance_read(:updated_at).to_i so it only changes if the file changes, not if anything else on the model changes. The problem you describe only happens if you are relying on Model.updated_at for the interpolation. Hello, Cameron. It doesn't work that way. The interpolation is using attachment.instance_read(:updated_at).to_i so it only changes if the file changes, not if anything else on the model changes. The problem you describe only happens if you are relying on Model.updated_at for the interpolation.

]]> By: Cameron Westland http://blog.tristanmedia.com/2009/09/using-amazons-cloudfront-with-rails-and-paperclip/comment-page-1/#comment-110 Cameron Westland Fri, 29 Jan 2010 16:14:15 +0000 http://blog.tristanmedia.com/?p=56#comment-110 Be careful with the updated_at interpolator if you're going to have any other attributes on the model. For instance. If you have :image and :name in the database. If you do Model#update_attribute(:name, "New name") it will update your Interpolation for the attachment. It will not however update the file name on the server so you're path and the actual file will be out of sync. Be careful with the updated_at interpolator if you're going to have any other attributes on the model. For instance. If you have :image and :name in the database. If you do Model#update_attribute(:name, "New name") it will update your Interpolation for the attachment. It will not however update the file name on the server so you're path and the actual file will be out of sync.

]]> By: Marco B http://blog.tristanmedia.com/2009/09/using-amazons-cloudfront-with-rails-and-paperclip/comment-page-1/#comment-60 Marco B Thu, 29 Oct 2009 08:33:42 +0000 http://blog.tristanmedia.com/?p=56#comment-60 Thanks for the post. I know CloudFront has a 24hours delay to refresh its content if you update a file of yours into S3, so the "change name" does the trick (renaming a file is also the only way to be sure that browser don't use a locally cached version). Nice way to implement this into paperclip, thanks again :) Thanks for the post.

I know CloudFront has a 24hours delay to refresh its content if you update a file of yours into S3, so the "change name" does the trick (renaming a file is also the only way to be sure that browser don't use a locally cached version).

Nice way to implement this into paperclip, thanks again :)

]]> By: Barry http://blog.tristanmedia.com/2009/09/using-amazons-cloudfront-with-rails-and-paperclip/comment-page-1/#comment-30 Barry Sun, 20 Sep 2009 01:41:53 +0000 http://blog.tristanmedia.com/?p=56#comment-30 I'm glad to hear it helped! I'm glad to hear it helped!

]]> By: Mike Champion http://blog.tristanmedia.com/2009/09/using-amazons-cloudfront-with-rails-and-paperclip/comment-page-1/#comment-29 Mike Champion Sun, 20 Sep 2009 01:22:20 +0000 http://blog.tristanmedia.com/?p=56#comment-29 Thanks for this post, it was very helpful in setting up our app with Cloudfront! Exactly what I was looking for. Thanks for this post, it was very helpful in setting up our app with Cloudfront! Exactly what I was looking for.

]]>