anchor.diff:  
   **simple-base-manifest.yml**
   
  -~~~
  +<pre>
   ---
   path: .
   domain: <%=vars.app_domain%>
  
positive.code:   path: ./flame/
    services:
    - redis-burnin-77
  ~~~
  
  Follow these general rules when using a multiple-application manifest:
  
  
negative.code: 
  To use `cf push` without an `-f` option, you must provide a manifest named `manifest.yml` in the current working directory.
  
  <pre class="terminal">
  $ cf push
  Using manifest file /path_to_working_directory/manifest.yml
  </pre>
  
  With the `-f` option, a path with no filename means that the filename must be `manifest.yml`.
  
  <pre class="terminal">
  $ cf push -f ./some_directory/some_other_directory/
  Using manifest file /path_to_working_directory/some_directory/some_other_directory/manifest.yml
  </pre>
  
  If the manifest is named something other than `manifest.yml`, use the `-f` option with both path _and_ filename.
  
  <pre class="terminal">
  $ cf push -f ./some_directory/some_other_directory/alternative_manifest.yml
  Using manifest file /path_to_working_directory/some_directory/some_other_directory/alternative_manifest.yml
  </pre>
  
  ## <a id='minimal-manifest'></a>An Example Manifest ##
  
  You can deploy applications without ever using a manifest. The benefits manifests may provide include consistency and reproducibility. When you want applications to be portable between different clouds, manifests may prove especially useful.
  
  Manifests are written in YAML. The manifest below illustrates some YAML conventions, as follows:
  
  * The manifest begins with three dashes.
  * The `applications` block begins with a heading followed by a colon.
  * The application `name` is preceded by a single dash and one space.
  * Subsequent lines in the block are indented two spaces to align with `name`.
  
  <pre>
  ---
  applications:
  - name: nifty-gui
    memory: 512M
    host: nifty
  </pre>
  
  A _minimal manifest_ requires only an application `name`. To create a valid minimal manifest, remove the `memory` and `host` properties from this example.
  
  Place your `manifest.yml` in the directory that contains the application files you want to push and run `cf push`. `cf push` searches the current directory for a manifest unless you specify another path with the `-p` option. 
  
  ## <a id='name'></a>Always Provide an Application Name to cf push ##
  
  