问题

在Rails 3.1(RC1)下默认情况下,sprockets在(dev)日志中往往相当详细:

 Started GET "/assets/application.css" for 127.0.0.1 at 2011-06-10 17:30:45 -0400
Compiled app/assets/stylesheets/application.css.scss  (5ms)  (pid 6303)


Started GET "/assets/application.js" for 127.0.0.1 at 2011-06-10 17:30:45 -0400
Compiled app/assets/stylesheets/default.css.scss  (15ms)  (pid 6303)

...
Started GET "/assets/default/header_bg.gif" for 127.0.0.1 at 2011-06-10 17:30:45 -0400
Served asset /default/header_logo.gif - 304 Not Modified  (7ms)  (pid 6303)
Served asset /default/header_bg.gif - 304 Not Modified  (0ms)  (pid 6246)
Served asset /default/footer_bg.gif - 304 Not Modified  (49ms)  (pid 6236)
...
 

我想减少详细程度或完全禁用它. 我假设有一种干净的方法来禁用或减少日志的详细性,在environment.rbdevelopment.rb中添加一个配置行,类似于config.active_record.logger = nil,其silectiveActiveRecord SQL语句.

  最佳答案

将以下代码放在config/initializers/quiet_assets.rb

 if Rails.env.development?
  Rails.application.assets.try(:logger=, Logger.new('/dev/null'))
  Rails::Rack::Logger.class_eval do
    def call_with_quiet_assets(env)
      previous_level = Rails.logger.level
      Rails.logger.level = Logger::ERROR if env['PATH_INFO'] =~ %r{^/assets/}
      call_without_quiet_assets(env)
    ensure
      Rails.logger.level = previous_level
    end
    alias_method_chain :call, :quiet_assets
  end
end
 

更新:现在也适用于Rails 3.2(以前的尝试修复before_dispatch现在我们将替换根架call)

更新:来自@macournoyer https://github.com/rails/rails/issues/2639#issuecomment-6591735 的正确Rack中间件解决方案(而不是脆弱的alias_method_chain)