Reorganize buildpacks, because order matters
Hardcode stack name

The newer heroku buildpackes (for example ruby/rails) use the STACK
variable for caching and cache busting (due to the cedar-14 stack).
Without a STACK envvar the caching system is broken and results in the
whole set of gems being reinstalled
Use offical PHP buildpack
Merge pull request #2 from yabawock/feature/stack

Provide stack name
Merge remote-tracking branch 'origin/master' into foreman
Merge pull request #3 from yabawock/feature/php

Use offical PHP buildpack
Merge branch 'master' into foreman

* master:
  Use offical PHP buildpack
Added erlang support
Updated README and AUTHORS
Added build step tests

- Added erlang build pack
- Added Wercker-CI support
Add test for plain Ruby app with MRI 2.1.3

Starting with 2.1.3, Rubies are placed in cedar/ subdirectory.
This test proves that up-to-date version of buildpack
is installed and uses correct stack.
Merge pull request #4 from jnv/tests-ruby

Add test for plain Ruby app with MRI 2.1.3
mkdir /root/bin

This fixes some issues I've seen around the web with php buildpack.  See:

* https://github.com/drmikecrowe/dokku-buildpack-php/commit/00cf93c2f3a60e11f9d4e81a7c110977dbddee41
* https://github.com/CHH/heroku-buildpack-php/issues/160
* https://github.com/romaninsh/dokku-alt-manager/issues/5
Merge pull request #5 from that0n3guy/master

mkdir /root/bin
Expose 5000
Move static apache at the end of the list

It's detected by the presence of .htaccess which is pretty common to many kind of apps.
Merge remote-tracking branch 'dokku-alt/master' into foreman