updates README.rb to include Jenkins URL advice 

A connection timeout occurs when responding to a POST /_builder if this isn't set. 
Janky goes to get the output from Jenkins but uses a URL sent from Jenkins instead of the config var.
Not sure if this is correct
Specify port and encoding for database
Added start messages to chat service

It's incredibly useful to know that Janky is succesfully handling
build requests based on GitHub notifications.
Parse 'template' value of GitHub /setup endpoint

- Allows Hubot or other clients to specify a template name instead
of relying on matching either the job name or the default
- /setup route response now contains job_config_path
- Updated docs
Update job configs / exclude template from ID

If an existing job is found, it should be allowed to update.
Without this, the Jenkins job configuration dashboard grows out of
hand with new jobs any time job templates change.

As such, MD5 job id should not include the job file contents.

There is enough uniqueness in job name generation without resorting
to reading job file contents to affect the MD5 id.

This is pretty problematic if minor tweaks are made to the Jenkins
job.xml.erb templates.  Consider changes such as modifying email
notifications, or enabling Chuck Norris, etc.

We refresh jobs automatically as part of an automated deployment,
but this will result in new MD5 job ids created in Jenkins.  This
is bad news, especially when there are many jobs.  All jobs are
now effectively duplicated and the history is now no longer
correlated between the runs, etc.
Update README.md
Somebody set up us the bomb.
Revert "Added start messages to chat service" /cc https://github.com/github/janky/pull/136

This reverts commit 9bf3a5ec574bee7717d41ead66bed0a7f7345f43.
Clarify the room name when using with Hipchat
remove exception middleware
change log tweaks
Truncate MD5 digests in job names to 12 characters

On Windows, file paths are limited to 260 characters (including the
drive letter and null terminator). Projects get checked out to
directories with names like:

    C:\<jenkins root>\workspace\<job name>

Including a 32-character MD5 digest (plus the repo owner and name) in
the job name significantly reduces the number of characters left for use
by the files in the repository. (For example, for
brightray/libchromiumcontent the job name is 61 characters long. When
combined with the drive letter, null terminator, and `\workspace\`, only
184 characters are left for paths within the repository itself.)

So now we truncate MD5 digests in job names to just the 12 most
significant hex digits. This is enough for building
brightray/libchromiumcontent (for now at least).
Include custom names in Jenkins job names

Previously, if you set up the same repo multiple times (e.g., to build
it on different platforms) like so:

    hubot ci setup github/janky janky18
    hubot ci setup github/janky janky19

...you'd end up with two nearly-indistinguishable Jenkins jobs with
names like:

    github-janky-2bce842af1a9
    github-janky-e89e28098c6a

With this change, the jobs will be easier to tell apart:

    janky18-2bce842af1a9
    janky19-e89e28098c6a

As an added bonus, the job names will usually be a bit shorter, giving
us still more breathing room on Windows before running into file path
length limits.
Update http.rb

Jenkins returns 201 when the build has been enqueued.
Accept both 302 and 201 response code
Update http.rb
latest version of sinatra-auth-github
cut a 0.9.15 release
set license in gemspec. closes #163