On Wednesday, March 21, 2012 10:44:46 AM UTC-7, Neil Middleton wrote: > > Is your staging app setup with a staging env? ie. RAILS_ENV and RACK_ENV > are both staging? >
> If not, you're going to be seeing some odd things with asset_sync. > Yes, both RAILS_ENV and RACK_ENV are set to "staging". Hmm, you have an interesting point here. But I'm pretty sure that RAILS_ENV is set to "production" during asset compilation. I would expect RACK_ENV to be irrelevant as rack shouldn't be loaded for asset compilation. Looking at heroku-buildpack-ruby<https://github.com/heroku/heroku-buildpack-ruby/blob/master/lib/language_pack/rails3.rb> they are manually setting RAILS_ENV. On Wednesday, 21 March 2012 at 17:33, Karl wrote: > > On Wednesday, March 21, 2012 9:18:26 AM UTC-7, Neil Middleton wrote: > > I wonder if you have an exception that's being swallowed somewhere along > the line. > > - Have you tried running the assets:precompile with a --trace? > > > Yes. Both locally and on heroku. > > Locally, all assets compile without error. > > On heroku, no errors reported, nothing in logs, but as I have stated in > previous message, the manifest.yml is just an empty erray. > > FYI, the manifest.yml after asset:precompile on heroku: > > --- {} > > > In the repo, it has all the correct assets. > > > - Have you tried the same code on a new Heroku app / S3 bucket to rule out > anything there? > > > No. I'll give it a try. > > Oddly enough, only the *staging* version of this app is giving me > trouble. The *production* version works as expected. So, in a way, I have > tried it on a different heroku account. Probably a good idea to try again. > > > > On Wednesday, 21 March 2012 at 16:08, Karl wrote: > > > 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. > > > -- > 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/-/gIGn0PjoWtYJ. > 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. > > > -- 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/-/rxRXjcDie7wJ. 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.
