asked this on April 02, 2012 09:44 PM
Trying to deploy a new Rails app for the first time, and it's not compiling on deploy and nothing in https://github.com/engineyard/engineyard-serverside/blob/master/lib... should be stopping it (pipelining is enabled in the application.rb, the application.rb is readable, there's no public/assets folder)
If you're deploying via the engineyard CLI, please try updating it via "gem update engineyard". It sounds like your local version of the CLI isn't in step with engineyard-serverside, and that could prevent the assets from being compiled properly on deploy.
Other things to check:
Seems like the symlink isn't getting created, and the shared assets folder is empty - what's my next step to fix that?
I took a look at your account and found two applications. One of them is a Rails 3.1 application that does have assets precompiled, so I knew that wasn't the problem app. The other one, however, was a rails 3.0 application that did not have assets compiled. If you look at the deploy logs, you'll see an entry four lines up from the bottom:
~> No 'assets:precompile' Rake task found. Skipping.
This is because the asset pipeline debuted in Rails 3.1, and the application in question is a Rails 3.0 application, according to its Gemfile. You need to upgrade your app to run on Rails 3.1.
Please file a ticket with us if you need any further assistance. Thank you!
Support Ticket System by Zendesk