I love FreshBooks. It makes my time tracking incredibly easy and my invoicing hassle free. That's not all; their website is extremely powerful but feels lightweight and friendly to use. As a software engineer, I really appreciate and expect my invoicing tool to be Web 2.0 and fun.
For it's free account, FreshBooks only allows you to have 3 clients. You can have any number of projects under those 3 clients but they set a cap in hopes you'll pay for their service. Well, I have more than 3 clients and I love freemium. FreshBooks allows you to have any number of freemium accounts. While it's a pain in the ass to have to switch between accounts for invoicing, it's worth the $20/month I'm saving...for now.
Another annoying thing about working with numerous freemium accounts is you can't quickly calculate numbers based on all projects you have. For instance, the total income from all projects or the total projected income for a single month. To remedy this, I wanted to create a lightweight Heroku app which would poll all my FreshBook freemium accounts and calculate some numbers, specifically the total hours spent and the total income for each project. FreshBooks has an API which allows me to do just that. +1 FreshBooks!
In this three-part series we'll build the app from the ground up, starting with Rack and then deploying to Heroku. Lets get started.
For the source of the entire project, head to https://github.com/mikepack/freshbooks_on_rack.
One consideration for this little project is the framework to use or if a framework is appropriate at all. I sought the following:
I love frameworks. They make most arduous tasks simple. I'm a Rails programmer but I realize for a project this small, Rails is way overkill. Other potential overkill frameworks include Merb, Sinatra and even Camping. I stumbled upon Waves, a resource oriented, ultra-lightweight framework. Unfortunately, Waves has been dead since 2009. So I decided to ditch the framework and go straight to Rack.
If you don't have Rack yet, install the gem:
gem install rack
Create a directory for your project:
Rack expects a configuration file to end in .ru:
You should now be able to run your Rack application from the command line:
Visit http://localhost:9292/ to see your app in action. It won't do anything yet (it'll throw an error), but the Rack basics are there.
FreshBooks has a great API. There's also a great corresponding gem which ruby-fies the API responses. The ruby-freshbooks gem is an isomorphic, flexible library with very little dependencies. freshbooks.rb is another FreshBooks API wrapper gem but has one major quip: it uses a global connection so you can't (naturally) pull in information from different FreshBooks accounts.
Heroku uses Bundler so create a Gemfile (you don't need the rack gem in your Gemfile):
Install the gem with Bundler:
Let's create a class which will handle our Rack implementation:
res = Rack::Response.new
res.write '<title>FreshBooks on Rack</title>'
All our class does so far is respond to a Rack call with a title tag. I use Rack::Response here to make things a little easier when it comes to the expected return value of our #call method. Take a look at this example for a reference on how to respond without using Rack::Response.
Now lets update our config.ru file to call our FBOnRack class:
FBOnRack#call will now be invoked when a request is made to our Rack app. Restart your Rack app (you'll need to do this on every code change), visit http://localhost:9292/ and you should see a blank page with a title of "FreshBooks on Rack".
Tada! You've just created a sweet Rack app, you should feel proud. In Part Two of this series, we'll take a look at how to work with the ruby-freshbooks gem. We'll generate simple, yet useful data and get our hands dirty in some metaprogramming.
Posted by Mike Pack on 05/01/2011 at 02:37PM