hexcodejosh

Updated this to remove the loop and only keep the explicit naming of the assets that need precompiled. This fixes the $c_green failure I was seeing in https://github.com/spree/spree_fancy/issues/41

Basically, install spree + spree_fancy, push to heroku, and use assets_sync to save assets to amazon s3. spree's built in s3 support handles products' assets correctly, but doesn't by itself...

The commit is here: https://github.com/hexcodejosh/spree_fancy/releases/tag/better_fix_for_missing_assets

For reference, my current Gemfile is: ``` source 'https://rubygems.org' ruby '2.0.0' # Bundle edge Rails instead: gem 'rails', github: 'rails/rails' gem 'rails', '4.0.0' # Postgres is required by heroku gem...

I'm seeing this issue right now with the 2-1-stable branch. I'm unable to compile spree_fancy's assets, and see the same $c_green error described above. If I neuter that line from...

sure, I'll create something from scratch and see if I can reproduce.

No dice.. can't reproduce it. Here's a log of what I did in case someone else stumbles on it. I'll keep looking for some diff that triggers it. From a...

Ah, I'm a victim of my own enthusiasm. If I modify my Gemfile to pull a tag from my fork of spree_fancy, I can reproduce it. #gem 'spree_fancy', :github =>...

So this fixed my issue: https://github.com/hexcodejosh/spree_fancy/releases/tag/better_fix_for_missing_assets