Initial commit
mongodb instead of hard code
start of adding a Job model
reference the new Job Model
fix syntax err.. seed jobs and then display to browser via api
connect to mongolab db
add more recs and see what connection spits out.. A L O T git diff!
add angular-resource#1.2.21 via bower
use angular resource to query a url - oh, and add chai too for our tests
using mocha and chai - testing that our db has at least one job, as we seed it with 4
bring mongoose/mongodb connection across from server (local connection) - and also the find code. Rename collection to jobsList as that is what this list is
looks like this is passing but it is not as expect never gets called, because mongoose call is async and the test is not and it finishes before the mongoose callback occurs
so mocha needs to indicae when a test is done, which if we do not call, defaults to a timeout of 2 seconds
now with done() being called it might work or it might not because we are not waiting for the connect to finish before we request our jobs
no now we wrapp the connect around the find, where the find is the callback to the connect
we need to test our seed functionality because as it stands our test was checking a seeded database, so we reset the db on each test and this will test if the db actually gets seeded
oops, different type of connection
We now seed the db with jobs after the reset, but we have to add a callback to
seedJobs (the part of the code to look for jobs and make sure there are some), but in order to
know when to call that callback we messily add it (call it) after inserting our last job.

We will add a third-party lib to help us deal with that more cleanly later
duh... needs to be original check against 0 (empty collection) and callback param does not take params.  Now tests pass. But the tests are becoming callback hell, so...
Using bluebird which gives us promises (like 'q') but there is also async.

But bluebird is supposed to be fast.