anchor.diff:  
   You can deploy multiple applications with one `cf push` command by describing them in a single manifest. In doing so, you need to pay extra attention to directory structure and path lines in the manifest.
   
  -Suppose you want to deploy two applications, `spark` and `flame`, and you want `cf` to create and start `spark` before `flame`. You accomplish this by listing `spark` first in the manifest.
  -
  -In this situation there are two sets of bits you want to push. Let’s say that they are `spark.rb` in the `spark` directory and `flame.rb` in the `flame` directory. One level up, the `fireplace` directory contains the `spark` and the `flame` directories along with the `manifest.yml` file. Your plan is to run `cf` from `fireplace`, where you know it can find the manifest.
  +Suppose you want to deploy two applications called respectively spark and flame, and you want `cf` to create and start spark before flame. You accomplish this by listing spark first in the manifest.
  +
  +In this situation there are two sets of bits you want to push. Let’s say that they are `spark.rb` in the spark directory and `flame.rb` in the flame directory. One level up, the fireplace directory contains the spark and the flame directories along with the `manifest.yml` file. Your plan is to run `cf` from `fireplace`, where you know it can find the manifest.
   
   Now that you have changed the directory structure and manifest location, the standard path line of `path: . ` no longer works. How can you ensure that `cf` finds the bits you want to push?
   
  
positive.code: 
  ### <a id='properties-block'></a>Properties ###
  
  The `properties` block consists of a heading, then one or more property/value pairs. Properties are evaluated and set at the moment that you run `cf push`. Unlike environment variables, properties do not persist from push to push.
  
  For example:
  
  ~~~
  properties:
   myprop1:frisbee
   myprop2:boomerang
  ~~~
  
  Properties can be combined with symbols. For example, if you define `myprop1` with the value "frisbee" in the properties block, you could specify a value of ``${myprop1}-${random-word}`` for the host attribute.
  
negative.code:   domain: <%=vars.app_domain%>
    path: ./flame/
    services:
      redis:
        label: redis
        provider: redis
        version: n/a
        plan: dev-sandbox
  ~~~
  