On Wednesday, March 21, 2012 6:38:20 AM UTC-7, Chap wrote: > > What do you mean by "the files are sync'd to S3"?
> Are you using a library to put them on S3? By default they should just > remain in your slug and be served from there. > > I have been using the asset_sync gem. I have tried allowing heroku to compile the assets and sync on deploy. And I have compiled locally, including the manifest.yml in the repo. Neither works. > If so I might try removing that library and see if you still have the > problem. > Already tried that. Removing asset_sync gem doesn't make a difference. When asset_sync is removed, it attempts to compile the assets, but doesn't complete, give no error messages (console or logs), overwrites manifest.yml with an empty array. Honestly, this shouldn't matter, because the builder should detect the existing public/assets/mainfiest.yml files and not even attempt to compile assets. I looked over the builder, and I don't see anything that stands out. BTW, I have several other heroku projects that I compile the assets locally using asset_sync to sync with S3, include mainfest.yml in the repo, and it works without fail. > > On Mar 20, 1:16 pm, Karl wrote: > > 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 ahttps://support.heroku.comticket 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/-/F6Kvelgv9pgJ. To post to this group, send email to heroku@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
