Heroku上的Rails 4应用程序，工作但日志错误答案

【问题标题】：Rails 4 App on Heroku, Works but Errors in LogHeroku上的Rails 4应用程序，工作但日志错误
【发布时间】：2013-03-12 03:42:16
【问题描述】：

该应用程序似乎正在运行，但我的日志中出现了这些错误。每次加载页面时，“/favicon.ico”、“/assets/application-34baf7d108c7408a8c110454dc57e8f6.js”和“/assets/application-e6b66fbbea8acd5eddb9fada1fa91c36.css”的日志中都会显示此问题。

另外，这个问题在开发中不会发生，只会在heroku上发生。

而且，即使它说的是 ruby/1.9.1，我只是检查了“heroku run ruby -v”并确认我正在运行“ruby 1.9.3p392（2013-02-22 修订版 39386）[x86_64-linux ]"

2013-03-12T03:34:50+00:00 app[web.1]: I, [2013-03-12T03:34:50.307770 #2]  INFO -- : Started GET "/favicon.ico" for 99.104.137.64 at 2013-03-12 03:34:50 +0000
2013-03-12T03:34:50+00:00 app[web.1]: F, [2013-03-12T03:34:50.322285 #2] FATAL -- : 
2013-03-12T03:34:50+00:00 app[web.1]: ActionController::RoutingError (No route matches [GET] "/favicon.ico"):
2013-03-12T03:34:50+00:00 app[web.1]:   vendor/bundle/ruby/1.9.1/bundler/gems/rails-f278deb712b1/actionpack/lib/action_dispatch/middleware/debug_exceptions.rb:21:in `call'
2013-03-12T03:34:50+00:00 app[web.1]:   vendor/bundle/ruby/1.9.1/bundler/gems/rails-f278deb712b1/actionpack/lib/action_dispatch/middleware/show_exceptions.rb:30:in `call'
2013-03-12T03:34:50+00:00 app[web.1]:   vendor/bundle/ruby/1.9.1/bundler/gems/rails-f278deb712b1/railties/lib/rails/rack/logger.rb:38:in `call_app'
2013-03-12T03:34:50+00:00 app[web.1]:   vendor/bundle/ruby/1.9.1/bundler/gems/rails-f278deb712b1/railties/lib/rails/rack/logger.rb:21:in `block in call'
2013-03-12T03:34:50+00:00 app[web.1]:   vendor/bundle/ruby/1.9.1/bundler/gems/rails-f278deb712b1/activesupport/lib/active_support/tagged_logging.rb:67:in `block in tagged'
2013-03-12T03:34:50+00:00 app[web.1]:   vendor/bundle/ruby/1.9.1/bundler/gems/rails-f278deb712b1/activesupport/lib/active_support/tagged_logging.rb:25:in `tagged'
2013-03-12T03:34:50+00:00 app[web.1]:   vendor/bundle/ruby/1.9.1/bundler/gems/rails-f278deb712b1/activesupport/lib/active_support/tagged_logging.rb:67:in `tagged'
2013-03-12T03:34:50+00:00 app[web.1]:   vendor/bundle/ruby/1.9.1/bundler/gems/rails-f278deb712b1/railties/lib/rails/rack/logger.rb:21:in `call'
2013-03-12T03:34:50+00:00 app[web.1]:   vendor/bundle/ruby/1.9.1/bundler/gems/rails-f278deb712b1/actionpack/lib/action_dispatch/middleware/request_id.rb:21:in `call'
2013-03-12T03:34:50+00:00 app[web.1]:   vendor/bundle/ruby/1.9.1/gems/rack-1.5.2/lib/rack/methodoverride.rb:21:in `call'
2013-03-12T03:34:50+00:00 app[web.1]:   vendor/bundle/ruby/1.9.1/gems/rack-1.5.2/lib/rack/runtime.rb:17:in `call'
2013-03-12T03:34:50+00:00 app[web.1]:   vendor/bundle/ruby/1.9.1/bundler/gems/rails-f278deb712b1/activesupport/lib/active_support/cache/strategy/local_cache.rb:72:in `call'
2013-03-12T03:34:50+00:00 app[web.1]:   vendor/bundle/ruby/1.9.1/bundler/gems/rails-f278deb712b1/railties/lib/rails/engine.rb:511:in `call'
2013-03-12T03:34:50+00:00 app[web.1]:   vendor/bundle/ruby/1.9.1/bundler/gems/rails-f278deb712b1/railties/lib/rails/application.rb:96:in `call'
2013-03-12T03:34:50+00:00 app[web.1]:   vendor/bundle/ruby/1.9.1/gems/rack-1.5.2/lib/rack/content_length.rb:14:in `call'
2013-03-12T03:34:50+00:00 app[web.1]:   vendor/bundle/ruby/1.9.1/gems/thin-1.5.0/lib/thin/connection.rb:81:in `block in pre_process'
2013-03-12T03:34:50+00:00 app[web.1]:   vendor/bundle/ruby/1.9.1/gems/thin-1.5.0/lib/thin/connection.rb:79:in `catch'
2013-03-12T03:34:50+00:00 app[web.1]:   vendor/bundle/ruby/1.9.1/gems/thin-1.5.0/lib/thin/connection.rb:79:in `pre_process'
2013-03-12T03:34:50+00:00 app[web.1]:   vendor/bundle/ruby/1.9.1/gems/thin-1.5.0/lib/thin/connection.rb:54:in `process'
2013-03-12T03:34:50+00:00 app[web.1]:   vendor/bundle/ruby/1.9.1/gems/thin-1.5.0/lib/thin/connection.rb:39:in `receive_data'
2013-03-12T03:34:50+00:00 app[web.1]:   vendor/bundle/ruby/1.9.1/gems/eventmachine-1.0.3/lib/eventmachine.rb:187:in `run_machine'
2013-03-12T03:34:50+00:00 app[web.1]:   vendor/bundle/ruby/1.9.1/gems/eventmachine-1.0.3/lib/eventmachine.rb:187:in `run'
2013-03-12T03:34:50+00:00 app[web.1]:   vendor/bundle/ruby/1.9.1/gems/thin-1.5.0/lib/thin/backends/base.rb:63:in `start'
2013-03-12T03:34:50+00:00 app[web.1]:   vendor/bundle/ruby/1.9.1/gems/thin-1.5.0/lib/thin/server.rb:159:in `start'
2013-03-12T03:34:50+00:00 app[web.1]:   vendor/bundle/ruby/1.9.1/gems/rack-1.5.2/lib/rack/handler/thin.rb:16:in `run'
2013-03-12T03:34:50+00:00 app[web.1]:   vendor/bundle/ruby/1.9.1/gems/rack-1.5.2/lib/rack/server.rb:264:in `start'
2013-03-12T03:34:50+00:00 app[web.1]:   vendor/bundle/ruby/1.9.1/bundler/gems/rails-f278deb712b1/railties/lib/rails/commands/server.rb:80:in `start'
2013-03-12T03:34:50+00:00 app[web.1]:   vendor/bundle/ruby/1.9.1/bundler/gems/rails-f278deb712b1/railties/lib/rails/commands.rb:80:in `block in <top (required)>'
2013-03-12T03:34:50+00:00 app[web.1]:   vendor/bundle/ruby/1.9.1/bundler/gems/rails-f278deb712b1/railties/lib/rails/commands.rb:75:in `tap'
2013-03-12T03:34:50+00:00 app[web.1]:   vendor/bundle/ruby/1.9.1/bundler/gems/rails-f278deb712b1/railties/lib/rails/commands.rb:75:in `<top (required)>'
2013-03-12T03:34:50+00:00 app[web.1]:   bin/rails:4:in `require'
2013-03-12T03:34:50+00:00 app[web.1]:   bin/rails:4:in `<main>'

【问题讨论】：

标签： ruby-on-rails heroku asset-pipeline thin ruby-on-rails-4

【解决方案1】：

我摆脱了错误，我在我的 config/enviroments/production.rb 中做到了这一点

-  config.assets.compile = false
+  config.assets.compile = true

【讨论】：

【解决方案2】：

作为解决方案的替代方案，您可以在本地编译资产，然后将它们发送到 heroku...

$ rake assets:precompile
$ git add -A
$ git commit -m 'compiled assets'
$ git push heroku master

我在 CI 步骤中执行此操作

【讨论】：