Article

Hey look, another blog post! This one’s about an odd asset pipeline thing we found yesterday:

I have a love/hate relationship with the asset pipeline. Ok, it's mostly hate. I applaud what it tries to do, but it takes something relatively simple - javascript and CSS - and makes it painful, mostly by making deploys take forever (even with turbo-sprockets-rails3 ). For example, I was working on something yesterday and doing deploys to the staging environment. I noticed that it took forever to be able to start serving requests. Passenger-status showed all three instances were running, and were all stuck serving their first request. A little digging revealed that there were a bunch of node.js processes running compiling assets! What the?! I thought I was precompiling everything! Nope, apparently not. After a little digging, I found this setting: config.assets.compile = true Set that to false and redeployed, and all of a sudden, I was seeing 500 responses for assets that...

Full article: http://railsmachine.com/articles/2013/03/08/watch-that-fi...