I fixed up tweets to be cached for the last four hours, and this should all play nice on Heroku. I also added specs and some error handling in case Twitter gets angry again. I tried to cache the last shot from Dribble, but that didn't play nice...so I backed off there.
You should look things over and let me know if you have questions before merging and deploying it.
getting specs wired up
using rspec and stuff
document the specs
Bring back the tweets...
- using ActiveSupport Cache (in memory only) to store last tweets
- last tweet will be stored for four hours by default
- bring in guard to speed up dev with fast spec runs
- show the time out message for tweets only if there wasn't a tweet
make sure we don't die if Twitter blows up