Page last updated:
Buildpacks provide framework and runtime support for your applications. Buildpacks typically examine user-provided artifacts to determine what dependencies to download and how to configure applications to communicate with bound services.
When you push an application, Cloud Foundry automatically detects which buildpack is required and installs it on the Diego cell or Droplet Execution Agent (DEA) where the application needs to run.
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 application.
Cloud Foundry includes a set of system buildpacks for common languages and frameworks. This table lists the system buildpacks.
|Name||Supported Languages, Frameworks, and Technologies||GitHub Repo|
Grails, Play, Spring, or any other JVM-based language or framework
Ruby, JRuby, Rack, Rails, or Sinatra
Cake, Symfony, Zend, Nginx, or HTTPD
Django or Flask
For general information about using buildpacks, see Using Buildpacks.
For general information about customizing existing buildpacks and developing new buildpacks, see Developing Buildpacks.View the source for this page in GitHub