3 ms·
I believe that in Rails 3.1 they're including a fix for this, so work arounds like this won't be necessary anymore :)
by Oompa 16y ago
I believe that in Rails 3.1 they're including a fix for this, so work arounds like this won't be necessary anymore :)
- 2is10 16y agoGot a link to details? I'd be surprised, since any correct solution requires two-stage deployment and keeping old assets around. These capabilities are beyond the scope of a web server framework. The Rails team could certainly educate Rails developers and choose conventions that make correctness easier.
- deleted 16y ago[deleted]