I don't post much around here, but @bpmilne suggested that having a small application to demo our new scheduled transactions endpoints would not be a bad idea -- so I wrote one in my favorite web framework; Rails.
The application is meant to serve as a basic example and as such I don't handle any API errors gracefully (Rails will show an error page) but I plan to add that in by the end of the week. It will not error out if you OAuth in before doing anything.
The Heroku deployment is left up to the user as it's trivial for anyone mildly computer literate. I provide a tutorial in the GitHub readme -- more can be learned by doing something yourself which is why it walks you through adding Heroku support to the app as opposed to just configuring it.
You can find the project here on GitHub.
Things to note
config/initializers/dwollavars.rb to change the
redirect parameter if you are using the non-standard Rails port or ngrok or a domain or whatnot
app/controllers/dashboard_controller.rb holds all of the application logic
Technical jargon and things that generally make people sleepy
- Did this from scratch, the user's
oauth_token are stored in the default rails
- The session is encrypted with the keys located in
config/secrets.yml. Change these and keep them private if you plan on exposing this application.
- There is no database; logon is handled by OAuth and the transactions are fetched from the API during every page load.
- The Heroku related gem is left as an exercise for the reader
Thank you all for your time!