Buildpacks provide framework and runtime support for apps. Buildpacks typically examine your apps to determine what dependencies to download and how to configure the apps to communicate with bound services.
When you push an app, Cloud Foundry automatically detects an appropriate buildpack for it. This buildpack is used to compile or prepare your app for launch.
Note: Cloud Foundry deployments often have limited access to dependencies. This limitation occurs when the deployment is behind a firewall, or when administrators want to use local mirrors and proxies. In these circumstances, Cloud Foundry provides a Buildpack Packager app.
The following topics discuss different usage scenarios for buildpacks in Cloud Foundry:
- How Buildpacks Work in Cloud Foundry
- Stack Association
- Pushing an Application with Multiple Buildpacks
- Using a Proxy
- Supported Binary Dependencies
- Production Server Configuration
For information about the existing buildpacks that Cloud Foundry supports, see System Buildpacks.
You can find a list of unsupported, community-created buildpacks here: cf-docs-contrib.
For information about customizing existing buildpacks and developing new buildpacks, see Customizing and Developing Buildpacks.
For information about updating and releasing a new version of a Cloud Foundry buildpack through the Cloud Foundry Buildpacks Team Concourse pipeline, see Using CI for Buildpacks. You can use this as a model when working with Concourse to build and release new versions of your own buildpacks.Create a pull request or raise an issue on the source for this page in GitHub