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
I'm a bit of a noob and don't know how to navigate around this issue.
I would be most appreciative if I got some guidance or help on this.
App runs fine locally but when deploying to heroku I get a mouth full
of fail - I am seeing the following error when I run heroku rake
db:migrate
rake aborted
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.
