在Ruby on 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)
...
我想减少它的冗长程度，或者完全禁用它。
我假设在这两种环境中都可以通过添加配置行来禁用或减少日志记录的冗长性。Rb或发展。Rb类似于config.active_record。logger = nil沉默ActiveRecord 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
更新:它现在也适用于Ruby on Rails 3.2(以前的尝试修复了before_dispatch，现在我们将改为根机架调用)
更新:一个合适的机架中间件解决方案(而不是脆弱的alias_method_chain)来自@macournoyer https://github.com/rails/rails/issues/2639#issuecomment-6591735
很多人对config.assets.logger = false的用法感到困惑。下面是它能做什么和不能做什么。
根据源文件:
将config.assets.logger设置为false将关闭服务的资产日志记录。
然而，这可能不是你想的那样。它只禁止sprocket“服务”日志，而不是Ruby on Rails actionpack请求日志。Ruby on Rails维护者在这里清楚地解释了这一点:
https://github.com/rails/rails/issues/4569#issuecomment-3594500
以链路为例，这样的日志是被禁用的:
已服务资产/jquery.同位素.js - 304未修改(0ms)
但像这样的对数不是
Started GET "/assets/jquery.同位素.js?Body =1" at 2012-01-20 23:16:46 -0500
