如何在Ruby on Rails 3.1中禁用资产管道(链轮)消息的日志记录?

问题描述

默认情况下，在Ruby on Rails 3.1(RC1)下，链轮在(dev)日志中往往非常冗长:

Sprockets tends to be quite verbose in the (dev) log by default under Ruby on Rails 3.1 (RC1):

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)
...

我想降低详细程度或完全禁用它.

I'd like to either reduce the level of verbosity or disable it altogether.

我假设有一种干净的方法可以通过在environment.rb或development.rb中添加类似于config.active_record.logger = nil的配置行来禁用或减少日志记录的冗长性，从而使ActiveRecord SQL语句静音.

I'm assuming there is a clean way to disable or reduce the verbosity of the logging by adding a config line in either environment.rb or development.rb similar to config.active_record.logger = nil which silences ActiveRecord SQL statements.

推荐答案

将以下代码放入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，现在我们打算使用根机架call)

Updated: It now works for Ruby on Rails 3.2 too (previous attempt fixes before_dispatch, and now we're going for the root rack call instead)

更新:来自@macournoyer https://github.com/rails/rails/issues/2639#issuecomment-6591735

Update: A proper Rack middleware solution (instead of fragile alias_method_chain) from @macournoyer https://github.com/rails/rails/issues/2639#issuecomment-6591735

这篇关于如何在Ruby on Rails 3.1中禁用资产管道(链轮)消息的日志记录?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！