Verbose Output From rake assets:precompile

Undistraction picture Undistraction · Nov 13, 2012 · Viewed 14.7k times · Source

I've just started using the asset_sync gem and my assets seem to be being compiled out of order, with Sass files unabled to access variables defined in other Sass files. What would really help me narrow down the issue is being able to see exactly what is going on during precompilation, but both rake assets:precompile and heroku run rake assets:precompile doesn't seem to offer a verbose option. All I get is some higher level output followed by a rake aborted! and a stack trace. Tailing heroku logs gets me nothing, so how can I get a more detailed log of what is going on during asset precompilation on Heroku?

Answer

Undistraction picture Undistraction · Nov 15, 2012

Turns out a combination of the following gets you some more verbocity. You get output when a file is precompiled, but not as it is being precompiled, so if it hangs you can't see what it's choked on.

  1. Use the --trace flag

    $ heroku run rake assets:precompile --trace

  2. Set the log to use STDOUT in production.rb:

    config.logger = Logger.new(STDOUT)