Given the read-only 
filesystem: http://docs.heroku.com/constraints#read-only-filesystem

...and the fact that "javascript_include_tag :some, :stuff, :cache => true" 
doesn't seem to work reliably on Heroku with Rails 3...

...and the fact that I have lots of separate javascript and css files that 
are slowing my site down: http://developer.yahoo.com/performance/rules.html

...I'm looking into a few possible ways to package these assets for 
deployment on Heroku:

https://github.com/amasses/heroku_asset_packager
https://github.com/mgomes/heroku_asset_cacher
https://github.com/documentcloud/jammit
https://github.com/ddollar/asset-resource
https://github.com/jnicklas/liability
...etc, etc etc...

...but none of them seem 100% ideal, and I'm not sure what to try using. 

Is there a preferred method of packaging assets in a Rails 3 app on Heroku?

Thanks!
- Trevor

-- 
You received this message because you are subscribed to the Google Groups 
"Heroku" group.
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