anchor.diff:  [j]: ./java-tips.html
   [n]: ./node-tips.html
   [r]: ./ruby-tips.html
  -[u]:../../buildpacks/
  +[u]: ./custom.html
   
   ## <a id='auto-vs-manual'></a>Auto-configuration of Service Connections##
   
  
positive.code: You can create [custom buildpacks](./custom.html) to add support for the
  languages or frameworks of your choice.
  
  Cloud Foundry stages application using buildpacks. Heroku developed the buildpack approach and made it available to the open source community.
  
  Cloud Foundry uses buildpacks to transform user-provided artifacts into runnable applications.  The functionality of buildpacks varies, but many of them examine the user-provided artifact in order to properly download needed dependencies and configure applications to communicate with bound services.  Heroku developed the buildpack approach and Cloud Foundry embraces it.
  
  
negative.code: title: Buildpacks
  ---
  
  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 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]
  