Removing the Rails 3 runtime asset compilation fallback about heroku-buildpack-ruby HOT 3 CLOSED

@toolmantim - Could you provide some more details on how newrelic is misbehaving in this case? We had several reports of this type of issue a few months ago (newrelic triggering the application to connect to the db during the precompile step which causes an error on heroku). I was under the impression we'd resolved them in the last several versions of the agent. The problem definitely stems from an interaction with the app code. Most heroku apps don't suffer this problem, and none of my heroku apps (or test apps I created to debug this) ever experienced this error, which has made it difficult to pin down the root cause.

Any help or insight you can provide is appreciated. Also which version of the newrelic gem are you using when you experience this?

Thanks,
Sam

from heroku-buildpack-ruby.

@samg have a link to the relevant issue? Let's continue the discussion there.

But basically, this is with newrelic_rpm 3.3.4.1 and Rails 3.2.3. The only way I could get asset compilation not to throw an error on deploy was to do as the dev article says, and add the following to application.rb:

config.assets.initialize_on_precompile = false

from heroku-buildpack-ruby.

@toolmantim I have several apps that fail on the asset compilation step and correctly fallback to compiling on the fly. In my cases, they're super small apps that I "just want to work". You need to add that line either way

config.assets.initialize_on_precompile = false

If we took this functionality away a number of apps that rely on the behavior would start failing on their next deploy and not due to something they did. Seems bad to just remove this behavior after it has existed for so long. I'm closing this issue as being inactive, and since the bug actually looks like it is in the 3rd party libraries.

from heroku-buildpack-ruby.