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.
we’ve been using Rails 3.0 for some time. We would use jammit to compile the assets which would then be stored in /public/assets for deployment only
Problem is, we recently upgraded to Rails 3.2.2 and now Jammit is compiling the assets in the source directories which is making a mess.
Anyone else experience this. What’s the right way to move from Rails 3.0 w jammit to Rails 3.2.2?
Thanks
Rails 3.1 and higher replace most of the functionality of Jammit, with a built-in process known as the Asset Pipeline. It’s is way cool, and also a pretty significant change.
There’s a line in
app/config/application.rb(for new Rails apps)Setting this to false should restore you to ancient history. But think about migrating the code — it’s not that hard, and more and more gems are expecting/depending on it.