I filed a support ticket with heroku yesterday. They have confirmed there is a bug. For some reason, manifest.yml is not being detected.
On Monday, March 12, 2012 11:54:37 PM UTC-7, Andrew Lorente wrote: > > I'm sorry to say I haven't found a solution--but my heart leapt when I saw > your previous message. I agree that it sounds like the very same thing, so > at least we are not alone! > > On Mon, Mar 12, 2012 at 7:34 PM, Karl wrote: > >> Can't help much, but I'm having a very similar problem. I am 100% >> positive I have public/assets/manifest.yml in my master branch. But when >> pushed to heroku, it doesn't see it. And of course the app won't >> run because compiled assets are missing. >> >> Please let me know if you have found a solution. >> >> >> On Saturday, March 3, 2012 9:44:30 PM UTC-7, Andrew Lorente wrote: >>> >>> Hi, >>> >>> I'm having a bear of a time upgrading a pre-3.1 rails app to 3.2. I'ts >>> working locally, but on heroku no matter what I do, I get exceptions on >>> pageload: >>> >>> A ActionView::Template::Error occurred in posts#index: >>> application.css isn't precompiled >>> >>> Initially it wouldn't compile at all; per heroku's troubleshooting >>> tips<http://devcenter.heroku.com/articles/rails31_heroku_cedar#troubleshooting>I >>> added `config.assets.initialize_on_ >>> **precompile = false` to config/application.rb . Now when I push to >>> heroku, the output log appears to be successfully precompiling my assets: >>> >>> $ git push heroku master >>> Counting objects: 17, done. >>> Delta compression using up to 4 threads. >>> Compressing objects: 100% (9/9), done. >>> Writing objects: 100% (9/9), 1.23 KiB, done. >>> Total 9 (delta 7), reused 0 (delta 0) >>> >>> -----> Heroku receiving push >>> -----> Ruby/Rails app detected >>> -----> Installing dependencies using Bundler version 1.1.rc.7 >>> Running: bundle install --without development:test --path >>> vendor/bundle --binstubs bin/ --deployment >>> Fetching gem metadata from https://rubygems.org/....... >>> {{snip bundle install}} >>> Your bundle is complete! It was installed into ./vendor/bundle >>> Cleaning up the bundler cache. >>> -----> Writing config/database.yml to read from DATABASE_URL >>> *-----> Preparing app for Rails asset pipeline >>> Running: rake assets:precompile* >>> -----> Rails plugin injection >>> Injecting rails_log_stdout >>> Injecting rails3_serve_static_assets >>> -----> Discovering process types >>> Procfile declares types -> web >>> Default types for Ruby/Rails -> console, rake, worker >>> -----> Compiled slug size is 20.7MB >>> -----> Launching... done, v30 >>> >>> But I still get "application.css isn't precompiled." >>> >>> I've tried manually precompiling my assets: >>> >>> $ RAILS_ENV=production bundle exec rake assets:precompile >>> /Users/andrewlorente/.rvm/**rubies/ruby-1.9.2-p290/bin/**ruby >>> /Users/andrewlorente/.rvm/**gems/ruby-1.9.2-p290@opinions/**bin/rake >>> assets:precompile:all RAILS_ENV=production RAILS_GROUPS=assets >>> >>> $ git add public/assets >>> $ git commit -m "precompiled assets" >>> $ git push heroku master >>> >>> But it has no effect. Perplexingly, I still see "Running: rake >>> assets:precompile" in the heroku slug compilation output, even though >>> in this case I have a public/assets/manifest.yml and the heroku docs say I >>> should see "Detected manifest.yml, assuming assets were compiled locally >>> ". >>> >>> It almost looks like heroku is expecting/putting manifest.yml somewhere >>> other than public/assets, but I don't have much evidence to support that. >>> >>> Thanks for any help you can suggest! >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "Heroku" group. >> To view this discussion on the web visit >> https://groups.google.com/d/msg/heroku/-/745SiM0ostAJ. >> To post to this group, send email to [email protected]. >> To unsubscribe from this group, send email to >> [email protected]. >> For more options, visit this group at >> http://groups.google.com/group/heroku?hl=en. >> > > -- You received this message because you are subscribed to the Google Groups "Heroku" group. To view this discussion on the web visit https://groups.google.com/d/msg/heroku/-/Fpigy5_KP5QJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
