Rails 3.2.2 app, on cedar, using ruby 1.9.3 with asset_sync gem to sync 
assets to S3. When I 'bundle exec rake assets:precompile' on my dev 
machine, asset_sync works just as expected.

However, the same project when pushed to Heroku skips some of the asset 
files. Just so I'm clear, these assets files are specified using 
'config.assets.precompile += []'. Here is the exact code in production.rb:


  config.assets.precompile += [ 'print.css',

                                'api_docs.css',

                                'not_auto_loaded/tester.js',

                                'not_auto_loaded/unauth_web_connect.js',

                                'not_auto_loaded/installation.js',

                                'not_auto_loaded/token_recovery.js'

                                ]

Print.css, api_docs.css, installation.js, and token_recover.js compile just 
fine and asset sync sends them on their merry way to S3. But *nothing* I 
have tried over the past two days will get unauth_web_connect.js or 
tester.js to compile on heroku. No errors are reported during slug 
compilation or in the logs.

Token_recovery.js.coffee and installation.js.coffee compile just fine, and 
appear on S3 as expected, digests and all.

Unauth_web_connect.js is a coffeescript file (unauth_web_connect.js.coffee) 
that resides in 'app/assets/javascript/not_auto_loaded/'.

I have tried, and it did not fix:

   - changing the names of the xxx.js.coffee files 
   - reducing the javascript in xxx.js.coffee files down to just 'alert 
   "home"' 
   - changing the order in config.assets.precompile 
   - removing the xxx.js.coffee file and re-creating it 

I'm out of 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/-/rMBXKfYthTAJ.
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.

Reply via email to