in cases where the tar already contains app, this was useful

to maintain the minimal nature of buildstep, just added a comment instead of code on how to do this
Make sure libreadline5 is installed.  Closes GH-93
Test building application images
Test running applications images
Run tests on wercker.com
Merge pull request #106 from darkpixel/GH-93-libreadline5

Make sure libreadline5 is installed.  Closes GH-93
Merge pull request #110 from yabawock/feature/wercker

Test building and running application images
Merge pull request #52 from bosky101/patch-1

in cases where the tar already contains app, this was useful
Switch to cedarish cedar-14 stack image
Use flynn buildpack installer

The flynn buildpack installer allows installing a specific version of a buildpack giving more control over the final buildstep environment.

See https://github.com/flynn/flynn/blob/master/slugbuilder/builder/install-buildpack for the upstream source
Modernize the builder

* Uses the buildpack installer for custom buildpacks
* Uses helpers to format the output
* Uses the environment variables for the start & exec commands
Remove old buildchain
Update Authors, License and add changelog
Remove preinstalled custom buildpacks
Fix installation of custom buildpacks
Upgrade PHP, Java, Scala & Gradle buildpacks
Add ENV_DIR support

Prepare buildstep to support the ENV_DIR feature that allows usinge the configuration variables during the compile phase. This change will need a change to dokku to put split the ENV file and insert it into the container as separate files.

This also makes the sourcing of the files in the .profile.d directory only take `*.sh` into consideration, matching the way that Heroku works.

See https://devcenter.heroku.com/articles/buildpack-api#bin-compile-usage for details on the ENV_DIR feature.

This implements #101 but also writes the config_vars to `00_config_vars.sh` so that defaults from the buildpacks get honored. That should be OK since the config_vars don't overwrite existing environment variables anymore. Removing this support is currently ill advised since some of the included buildpacks (Scala, Play, Grails) use this to set up paths and JVM options.

This commit is a combination of #99, #100 and #101 adjusted slightly for the new builder structure.
Source profile.d for interactive shell
Run as non-root user

Generate a random user on each deploy and run the compile step as well as the final application with this restricted account. This should solve the problems with the permissions in the PHP buildpack and the Bundler warning in the ruby buildpack.

References:
  * #88 - security?
  * #98 - Run apps as non-root user, take 2
  * #42 - Allow apps to run without root
Update test apps for latest setup