Yeah, Heroku should make this a lot easier. I experimented with one approach to this a while ago, and it seemed to work fine on my staging dyno. I haven't gotten around to actually running it in production yet, though, so use at your own risk:
https://gist.github.com/998124 Let me know how it goes! On May 29, 1:26 pm, S Wrobel <swro...@gmail.com> wrote: > I'd like my static assets to cache for longer. I think Heroku's default is > 12 hours, but considering that Rails adds the ?33253523 stuff to them to > indicate when a new version has been deployed, there's no reason not to > cache them for months if not years. 12 hours seems way too short for me. > Does anyone have any feedback on whether this is wise to do, and also how to > override it? -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to heroku@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
