This is an experimental feature. In this case, this means: we offer long-term support for the ability to have custom buildpacks, but you are responsible for maintaining your custom buildpack.
Cloud Foundry (the underlying open source project behind cloud.gov) uses buildpacks to allow your applications to be deployed.
cloud.gov officially supports a set of buildpacks, and it also allows you to provide your own.
For example, if you want to use the “R” buildpack, you can push your code by typing:
cf push myapp -b https://github.com/alexkago/cf-buildpack-r
Once you push your code using a custom buildpack, cloud.gov cannot update it for you. You are responsible for keeping it up to date. Please see this description of responsibilities.
Example custom buildpacks
If you can’t do that, Cloud Foundry is capable of deploying multi-language projects with a custom buildpack,
cf-buildpack-multi. This buildpack applies any buildpacks listed in the
.buildpacks file. Multi-buildpack deploys can be difficult to debug because
cf-buildpack-multi hides the error logs.
cloud.gov does not allow the use of
sudo inside of buildpacks. If your app depends on a library that is
apt-get installable, you can use the CF flavor of
apt-buildpack, which is a custom buildpack. This can work with