Closed mcolyer closed 11 years ago
This was really a variation on #11. For some reason the first deploy of turbosocket would always work as expected but then second deploy would fail with the above error.
However once I realized that I wasn't using precompiled assets in production by accessing the sprockets environment directly I create a wrapper to properly handle using precompiled assets. I'm not sure why rails doesn't provide an API for this, it's definitely not clear that Sprockets doesn't do this for you automatically.
I use the bulletproof css syntax with fontawesome.
Unfortunately using this gem in conjunction with heroku causes assets with query strings (like those found in fontawesome) to raise "Sprockets::Helpers::RailsHelper::AssetPaths::AssetNotPrecompiledError:fontawesome-webfont.eot?#eotfix isn't precompiled" in production.
Any ideas of what could be causing this?