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: [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: You can create [custom buildpacks](./custom.html) to add support for the
  languages or frameworks of your choice.
  
  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.
  
  