Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
The heroku cedar precompile my assets implicitly, even though I have written:
config.assets.enabled = false
How to disable the assets feature?
The problem is that the application config isn’t available when the slug is compiled. This was recently addressed with http://devcenter.heroku.com/articles/labs-user-env-compile but I’m not sure if that will help here.
For more info on the pipeline on Heroku take a look at http://devcenter.heroku.com/articles/rails31_heroku_cedar
It looks like the easiest way to prevent asset compilation is to put a file in public/assets/manifest.yml – would presume contents is irrelevant but also disable it via config.assets.enabled just in case.