anchor.diff:  command: bundle exec rake VERBOSE=true
   ~~~
   
  +For some types of application, you must provide a start command, either in a manifest or using the `-c` command-line option. This is true of node.js applications, for example.
  +
   ### <a id='domain'></a>The domain attribute ###
   
   Applications are always pushed to a particular Cloud Foundry instance, and each Cloud Foundry instance has a default domain.
   
  -When the domain line is omitted, `cf` assigns your application to the default domain. Use the domain line when you want your application to be served from a domain other than the default.
  +When you omit the domain line, `cf` assigns your application to the default domain. Use the domain line when you want your application to be served from a domain other than the default.
   
   ~~~
   domain: unique9876.example.com
   ~~~
   
  +### <a id='no-route'></a>The no-route attribute ###
  +
  +By default, Pivotal CF assigns a route to every application. This is inappropriate for workers, which applications that run in the background, providing services to other applications. In your manifests, always include the `no-route` line in the description of a worker application. The `no-route` attribute always appears with a value of `true`:
  +
  +~~~
  +no-route: true
  +~~~
  +
  +For more about workers, see [Describing Multiple Applications with One Manifest] (#multi-apps) below.
  +
  +
   ### <a id='env-block'></a>Environment variables ###
   
  -The `env` block consists of a heading, then one or more environment variable/value pairs. An application is deployed to a container on the server. The variables belong to the environment of the container.
  +The `env` block consists of a heading, then one or more environment variable/value pairs.
   
   For example:
   
  
positive.code: 
  The `services` block consists of a heading, then one or more service instance names.
  
  Service instance names are chosen by whoever creates the service. 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:
  
negative.code:   RACK_ENV: ${rails-env}
  ~~~
  
  `cf push` deploys the application to a container on the server. The variables belong to the container environment.
  
  While the application is running, `cf` allows you to operate on environment variables.
  
  * View all variables:
  