Comments for Tristan Media Blog http://blog.tristanmedia.com One can never have enough scripting languages: Notes on Perl, PHP, and Ruby Thu, 08 Dec 2011 19:07:14 +0000 hourly 1 http://wordpress.org/?v=3.0.4 Comment on Using Amazon’s CloudFront with Rails & Paperclip by Michael Hellein http://blog.tristanmedia.com/2009/09/using-amazons-cloudfront-with-rails-and-paperclip/comment-page-1/#comment-3099 Michael Hellein Thu, 08 Dec 2011 19:07:14 +0000 http://blog.tristanmedia.com/?p=56#comment-3099 Also, if you use rand in the Proc above, you'll be telling browsers to load the same file from different servers on each request, which is obviously not helpful for caching! Also, if you use rand in the Proc above, you'll be telling browsers to load the same file from different servers on each request, which is obviously not helpful for caching!

]]> Comment on Using Amazon’s CloudFront with Rails & Paperclip by Michael Hellein http://blog.tristanmedia.com/2009/09/using-amazons-cloudfront-with-rails-and-paperclip/comment-page-1/#comment-3098 Michael Hellein Thu, 08 Dec 2011 18:47:51 +0000 http://blog.tristanmedia.com/?p=56#comment-3098 I haven't tried using Paperclip with Cloudfront yet, but I was also considering something like Mike Larkin is suggesting to get around the requests-per-domain bottleneck. However, I don't think his approach will work, as the string interpolation should only happen once when the model is loaded. (Or am I mistaken?) Fortunately, :s3_host_alias also takes a Proc, so you could do: :s3_host_alias => Proc.new { "cdn#{rand(4)}.pixellent.com" } I also don't know if I would use rand, because you'd get a more even distribution by repeatedly iterating from 0-n (where n is the number of domains). On some percentage of requests, rand will give us all the same domain, and then we'd have no performance gain! I haven't tried using Paperclip with Cloudfront yet, but I was also considering something like Mike Larkin is suggesting to get around the requests-per-domain bottleneck. However, I don't think his approach will work, as the string interpolation should only happen once when the model is loaded. (Or am I mistaken?)

Fortunately, :s3_host_alias also takes a Proc, so you could do:

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

I also don't know if I would use rand, because you'd get a more even distribution by repeatedly iterating from 0-n (where n is the number of domains). On some percentage of requests, rand will give us all the same domain, and then we'd have no performance gain!

]]> Comment on Using Amazon’s CloudFront with Rails & Paperclip by Colin Adams http://blog.tristanmedia.com/2009/09/using-amazons-cloudfront-with-rails-and-paperclip/comment-page-1/#comment-1462 Colin Adams Tue, 03 May 2011 00:53:13 +0000 http://blog.tristanmedia.com/?p=56#comment-1462 Thanks for this. I was looking for S3 stuff, but the ":default_style => :original" came in handy! Thanks for this. I was looking for S3 stuff, but the ":default_style => :original" came in handy!

]]> Comment on Using Amazon’s CloudFront with Rails & Paperclip by Dave Rapin http://blog.tristanmedia.com/2009/09/using-amazons-cloudfront-with-rails-and-paperclip/comment-page-1/#comment-1216 Dave Rapin Fri, 04 Mar 2011 16:11:33 +0000 http://blog.tristanmedia.com/?p=56#comment-1216 Great writeup, thanks a lot. Especially found the timestamp based on *file* modified date useful for cloudfront. I'm using this for the next version (still in development) of my open source photographer portfolio (http://grokphoto.org) Great writeup, thanks a lot. Especially found the timestamp based on *file* modified date useful for cloudfront.

I'm using this for the next version (still in development) of my open source photographer portfolio (http://grokphoto.org)

]]> Comment on Using Amazon’s CloudFront with Rails & Paperclip by Scott Carleton http://blog.tristanmedia.com/2009/09/using-amazons-cloudfront-with-rails-and-paperclip/comment-page-1/#comment-1170 Scott Carleton Fri, 18 Feb 2011 01:49:55 +0000 http://blog.tristanmedia.com/?p=56#comment-1170 Barry, Thanks for this post. Exactly what I was looking for! Barry,

Thanks for this post. Exactly what I was looking for!

]]> Comment on Rails 3, RSpec, Mongoid and Database Cleaner by Rafael Lima http://blog.tristanmedia.com/2010/07/rails-3-rspec-and-database-cleaner/comment-page-1/#comment-394 Rafael Lima Wed, 18 Aug 2010 19:38:44 +0000 http://blog.tristanmedia.com/?p=88#comment-394 If you do not use seed, you can try the code below config.before(:each) do Mongoid.master.collections.select {|c| c.name !~ /system/ }.each(&:drop) end If you do not use seed, you can try the code below

config.before(:each) do
Mongoid.master.collections.select {|c| c.name !~ /system/ }.each(&:drop)
end

]]> Comment on Rails 3, RSpec, Mongoid and Database Cleaner by Louis Rose http://blog.tristanmedia.com/2010/07/rails-3-rspec-and-database-cleaner/comment-page-1/#comment-290 Louis Rose Wed, 28 Jul 2010 15:55:31 +0000 http://blog.tristanmedia.com/?p=88#comment-290 Thanks very much! This is exactly what I was after, and you saved me some time wrestling with these gems. Cheers! Thanks very much! This is exactly what I was after, and you saved me some time wrestling with these gems. Cheers!

]]> Comment on Using Amazon’s CloudFront with Rails & Paperclip 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.

]]> Comment on Using Amazon’s CloudFront with Rails & Paperclip 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"

]]> Comment on Using Amazon’s CloudFront with Rails & Paperclip 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.

]]>