- Sinatra, OmniAuth, twitter gem, Heroku
- As little UI as possible, think CLI level
- Simple sorted display of all the users you have favorited or retweeted
- Little attention to rate limits (15 minute dumb cache), this will blow up on large initial datasets (for now)
- Probably live at http://how-i-tweet.herokuapp.com
- bake your favorite ruby gem env
- gem install bundler
- bundle install
Get your own Twitter app tokens from https://apps.twitter.com/app/new
TWITTER_CONSUMER_KEY=your_key TWITTER_CONSUMER_SECRET=your_secret rerun rackup
Else set those in secrets.yml. Recommend you don't commit that file!
Set your secrets with
heroku config:set TWITTER_CONSUMER_KEY=your_key
heroku config:set TWITTER_CONSUMER_SECRET=your_secret
git push heroku master
heroku open
Or visit http://your-app-name.herokuapp.com
- Need to handle hitting rate limits
- Pick a sensible cache strategy that accounts for favs and rts anywhere in the timeline
- Pick a cache for Heroku (continue to use file system for dev), options...