anchor.diff:  title: Buildpacks
   ---
   
  -Buildpacks are a convenient way of packaging framework and/or runtime support
  -for your application.
  +Buildpacks are packages that provide framework and runtime support for your 
  +applications.
   For example, by default Cloud Foundry does not support Python, or a Python
   framework like Django. Using a buildpack for Python and Django would allow you
   to add support for these at the deployment stage.
   
  -When an application written using one of these languages and frameworks is
  -pushed, the required buildpack is automatically installed on the Cloud Foundry
  -Droplet Execution Agent (DEA) where the application will run.
  +When you push an application, Cloud Foundry automatically installs the required 
  +buildpack on the Droplet Execution Agent (DEA) where the application needs to run.
   
   Cloud Foundry has three system buildpacks: one each for [Java]
   (https://github.com/cloudfoundry/java-buildpack), [Node.js]
  
positive.code: [p]: ./play-service-bindings.html
  [s]: ./spring-service-bindings.html
  
  ## <a id='java'></a>Java, Grails, Play and Spring ##
  
  * [Deploying Java applications](./java-tips.html)
  * [Configure Service Connections for Grails](grails-service-bindings.html)
  * [Configure Service Connections for Play](play-service-bindings.html)
  * [Configure Service Connections for Spring](spring-service-bindings.html)
  
  ## <a id='node'></a>Node.js ##
  
  * [Deploying Node.js applications](./node-tips.html)
  * [Configure Service Connections for Node](node-service-bindings.html)
  
  ## <a id='ruby'></a>Ruby ##
  
  * [Deploying Ruby applications](./ruby-tips.html)
  * [Configure Service Connections for Ruby](ruby-service-bindings.html)
  
negative.code: [j]: ./java-tips.html
  [n]: ./node-tips.html
  [r]: ./ruby-tips.html
  [u]: ./custom.html
  
  ## <a id='auto-vs-manual'></a>Auto-configuration of Service Connections##
  
  