anchor.diff:      redis-burnin-77
   ~~~
   
  +
  +When you want to deploy workers to provide background services to your regular applications, use a multiple-application manifest with a `no-route` line in each worker description.
  +
  +Anytime you have a multiple-application manifest, describe your applications completely in the manifest rather than using any command-line options with `cf push`. Otherwise, questions of precedence between the manifest and command-line options tend to become prohibitively complex.
  +
  +
   ## <a id='minimize-duplication'></a>Minimizing Duplication ##
   
   In manifests where multiple applications share settings or services, you begin to see content duplicated. While the manifests still work, duplication increases the risk of typographical errors which cause deployment to fail.
  
positive.code:   RACK_ENV: ${rails-env}
  ~~~
  
  While the application is running, `cf` allows you to operate on environment variables.
  
  * View all variables:
  
negative.code: 
  The `services` block consists of a heading, then one or more service instance names.
  
  Whoever creates the service chooses the service instance names. These names can convey logical information, as in `backend_queue`, describe the nature of the service, as in `mysql_5.x`, or do neither, as in the example below.
  
  ~~~
    services:
  