On Tuesday, March 20, 2012 8:51:24 AM UTC-7, richard schneeman wrote: > > So if you bash into your application, are your files also missing from > the dyno or can you see your the files? I'm curious if the files are > not being generated correctly, or just not being synced correctly. > > > $ heroku run bash > Running bash attached to terminal... up, run.1 > ~ $ ls public/assets > application-95bd4fe1de99c1cd91ec8e6f348a44bd.css > application.css manifest.yml > application-95bd4fe1de99c1cd91ec8e6f348a44bd.css.gz > application.css.gz rails-782b548cc1ba7f898cdad2d9eb8420d2.png > application-95fca227f3857c8ac9e7ba4ffed80386.js > application.js rails.png > application-95fca227f3857c8ac9e7ba4ffed80386.js.gz > application.js.gz > > What about your manifest.yml?
Yup, already tried that... manifest.yml is there. But... > > ~ $ cat public/assets/manifest.yml > rails.png: rails-782b548cc1ba7f898cdad2d9eb8420d2.png > application.js: application-95fca227f3857c8ac9e7ba4ffed80386.js > application.css: application-95bd4fe1de99c1cd91ec8e6f348a44bd.css > The manifest.yml is there, but the yaml is an empty array. What is happening is heroku still *attempts* to compile assets, but borks, overwrites my manifest.yml with a manifest.yml that is essentially an empty array (not an empty file, though). Have you opened a https://support.heroku.com ticket for this issue? Yes. Been a week, the issue was escalated, but still no response. Frustration ensues. The only workaround I have it to turn assets.compile = true, and it directs the user to the assets on S3, but they are not compiled/combined/gzip'd. Do you have any other ideas? -- 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/-/Unp8Kw9FFWoJ. 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.
