On Mon, Sep 19, 2011 at 2:23 PM, Rajarshi <[email protected]> wrote:
> config.serve_static_assets = true > > in production.rb I think this is a really bad idea. With this setting, the assets are served from the _rails_ server (running ruby code) while these are static files (with cache buster names) that can be server much more efficiently directly by the web server from the public/assets/ file system. From: http://spreecommerce.com/documentation/server_configuration.html "...config.serve_static_assets = true There is a good reason why this is disabled by default in Rails which is that Rails is not a general purpose web server. Servers such as Apache and Nginx are optimized for rapidly serving up static content. You should consider the advice of the Rails core team and let your webserver do what it does best (as described in the next section.) " Peter -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
