Adding additional info and error handling when attempting to discover a heroku app. This helps resolve an issue where the app may be mispelled or otherwise incorrect in .travis.yml and will now provide a more useful error than 403 Forbidden
removed begin block
Updated check app spec to match improved messages
Adding user instance variable
Revert "Adding user instance variable"

This reverts commit 36d120a710f8429fcfdfac3715f6e5a5c2b9b4f9.
Not calling user in message
Hackage support
Update README
Check auth and cabal check
Install cabal for Hackage deployments
Force push Cloud Control apps
switch openshift deployment-branch to current branch before pushing when app.deployment_branch is set
testing spec file
Fix up Pull Request #131

Fix library, and use stub in sepc
Merge pull request #113 from koterpillar/hackage

Add support for deploying to Hackage

Fixes #113

Conflicts:
	README.md
	lib/dpl/provider.rb
Merge pull request #95 from STRd6/improve-error-message-for-bad-app-configs

Adding additional info and error handling when attempting to discover a ...
Actually cache user object
Update bdist to bdist_wheel [skip ci]

Fixes #108
Accept dot-delimited CLI options as 2-level hash

This allows nested options on the command line up to 2 levels
Add New Relic deployment notification support

This should basically work.

To test CLI:

```
dpl --newrelic.app_name=myapp --newrelic.license_key='0123456789abcdef' <other_opts>
```

To test with `.travis.yml`:

```yaml
deploy:
  provider: engineyard
  api_key: "API KEY"
  newrelic:
    app_name: myapp
    license_key: '0123456789abcdef'
    description: "Deployed by Travis CI"
```

Ideally, dynamic values can be assigned to the deployment notification
payload (https://github.com/newrelic/newrelic_api/#deployment-notifications)
but no processing is done right now.
In other words, having some environment variables like
`$TRAVIS_BRANCH` be available in the `deploy.newrelic` section,
but I am not sure if this is possible.