Construct `Octonode` lazily and support per-app API hosts
support enterprise hosts a bit better
version bump for enterprise support
get token and api endpoint info from the api config
Merge pull request #29 from atmos/allow-per-app-github-api-rework

Better Enterprise Support
Add the message thread (if provided) into the deployment payload

Flowdock has message threading and exposes the particular thread via
a thread_id property on the [message user object](https://github.com/flowdock/hubot-flowdock/blob/3c23b0953b2c70749125c7568be3586830c68836/src/flowdock.coffee#L82).
This would be useful to have in the deployment payload for notifying back
to the original thread.
Rename thread to message_thread and only if using flowdock
Merge pull request #30 from kiratalent/threading

Add the message thread (if provided) into the deployment payload
fallback to the HUBOT_GITHUB_TOKEN, fixes #31
version bump
try getting the user directly for flowdock
filter out configuration based tokens and info
Use user.message over thread_id for flowdock adapter

I believe thread_id is from an older implementation and may be
deprecated. The message property is more appropriate.
Merge pull request #32 from kiratalent/get-message-from-right-place

Use user.message over thread_id for flowdock adapter
version bump
shuffle docs, document enterprise API support
Merge pull request #33 from atmos/more-docs

Document enterprise API support
Merge remote-tracking branch 'upstream/master'

Conflicts:
	README.md
	src/deployment.coffee