Merge pull request #3 from AEgan/egan-dev

sets your token and secret to make API calls
Merge pull request #4 from AEgan/egan-dev

Token and secret more explicit
Merge branch 'egan-dev'
merging to keep the streak alive and work on this thing
modifies API call to use consumer key and api token instead of hard coding the call
changes back to the 1.0 format. This is annoying
Merge branch 'egan-dev'
Why 1.0? I don't know. This API call won't be valid for long
gutted most of the passport stuff to attemp to get it up to 2.0
getting the correct response. Now for the tokens
almost there, need to send a post request to linkedin
filling out return method for home controller, adds method explaining what to do next but unsure of how to do it
changes variable names to match the paramater names in the API call
this does not work but I am pushing for demonstration tomorrow
Merge pull request #8 from AEgan/oauth

Oauth failing
gutted the controller and starting over
I got the access token.
saves the oauth token and removes debugging console logs
roadblock: we need access to this API by going here https://help.linkedin.com/app/api-dvr :octocat:
hides search form on hompage if you are not logged in, does not show login button if you are logged in
places the job title in the API call and puts API access information on the search results page
adds some css so it does not look as pathetic