Another approach if you're packaging assets like this anyway would be to upload them to S3 instead of adding them to the app. You could then use S3 as an asset host, and even take advantage of CloudFront as a CDN.
On Jan 13, 2011, at 12:49 PM, Trevor Turk wrote: > On Thursday, January 13, 2011 1:35:27 PM UTC, John Beynon wrote: > We use https://github.com/sbecker/asset_packager under Rails3 on Heroku - > works great for us, > > Run a rake task locally to package after any changes to js/css, commit to git > and then deploy > > Thanks for that. I've been playing with some stuff today, and came up with > this: > > https://gist.github.com/778234 > > Basically, I can use "rake deploy" to deploy to heroku, and it caches the > assets automatically. It's an interesting strategy, I think. I'm curious if > you guys have any opinion. > > - 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. -- 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.
