如何在Rails 3.1中禁用资产管道（链轮）消息的日志记录？

在Rails 3.1（RC1）下默认情况下，（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.rb或development.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

更新：现在也适用于Rails 3.2（以前的尝试修复了before_dispatch现在我们要改为根机架call ）

更新：来自@macournoyer的适当的Rack中间件解决方案（而不是脆弱的alias_method_chain ）https://github.com/rails/rails/issues/2639#issuecomment-6591735

---

看看https://github.com/evrone/quiet_assets，并将其包含到您的Gemfile中

对于lazy： gem 'quiet_assets', group: :development

---

对于Rails 3.2，将config.assets.logger = false添加到开发环境配置文件中，通常可在config/environments/development.rb 。 见＃4512

链接地址: http://www.djcxy.com/p/63553.html

上一篇: How to disable logging of asset pipeline (sprockets) messages in Rails 3.1?

下一篇: Best practices to handle routes for STI subclasses in rails