30 Jul '12, 10am

@natekontny hi chap, I've added some comments about your etag cache article on Rubyflow, might be worth a read:

How to bust your Rails etag cache on deployment. Posted by Nate on July 27, 2012 — 2 comments A simple tip to handle etag busting on deploying your Rails app. Comments “ ” This works fine provided you only have a single instance of your app running , otherwise that timestamp may be different for each instance, causing the etags to change depending on which instance is serving each request - therefore defeating the whole point of them. If you want to handle this properly, you'll want to use something like the current Git checkout hash, or a timestamp persisted in a file (I believe Capistrano does this) - then the ENV["RAILS_APP_VERSION"] variable is more suitable (purely semantics). I'm not sure either of those methods are available for Heroku though...ryantownsend - July 28, 2012 15:56 “ ” I've just confirmed Capistrano does indeed do this... it prints a revision hash into...

Full article: http://www.rubyflow.com/items/8007-how-to-bust-your-rails...

Tweets

A Path To Rails 4 With MiniTest::Spec : RubyFlow

rubyflow.com 06 Aug '12, 1am

are actually a popular with designers and stylists frequent now. Many celebrities have been spotted with such bags, additi...