Need to verify that eastwood is indeed the culprit, but it sounds like we're unable to precompile assets on heroku because the environment needs to be present during compilation. Wonder if there's a good way around this, because precompiling locally sucks.
jeremyruppel
commented
12 years ago
Need to verify that eastwood is indeed the culprit, but it sounds like we're unable to precompile assets on heroku because the environment needs to be present during compilation. Wonder if there's a good way around this, because precompiling locally sucks.
http://devcenter.heroku.com/articles/rails31_heroku_cedar#troubleshooting