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?
相关问题
- Question marks after images and js/css files in ra
- Using :remote => true with hover event
- Eager-loading association count with Arel (Rails 3
- I want to trace logs using a Macro multi parameter
- How to specify memcache server to Rack::Session::M
相关文章
- how do I log requests and responses for debugging
- Right way to deploy Rails + Puma + Postgres app to
- AWS S3 in rails - how to set the s3_signature_vers
- how to call a active record named scope with a str
- How to add a JSON column in MySQL with Rails 5 Mig
- Django/Heroku: FATAL: too many connections for rol
- “No explicit conversion of Symbol into String” for
- form_for wrong number of arguments in rails 4
In case a deploy fails during asset precompile phase and you want to debug it, you can force heorku to push without precompiling assets by adding an empty
public/manifest.yml
. This will allow you to run$heroku run rake assets:precompile --trace
as @Pedr described in his answer.See Is it possible to skip the asset precompile step for a single git push on Heroku? for more details.
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.
Use the --trace flag
$ heroku run rake assets:precompile --trace
Set the log to use STDOUT in production.rb:
config.logger = Logger.new(STDOUT)