anchor.diff:    timeout: 80
   </pre>
   
  -If the app has not started by the timeout limit you set, Cloud Foundry stops trying to start the app. You might want to increase the timeout length to ensure that very large apps have sufficient time to start.
  +If the app has not started by the timeout limit that you set, Cloud Foundry stops trying to start the app. You might want to increase the timeout length to ensure that very large apps have sufficient time to start.
   
   The command line option that overrides this attribute is `-t`.
   
  
positive.code: file in the current working directory.
  Use the `-f` option to provide a non-standard manifest location or filename.
  
  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:
  
  
negative.code:   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 
  that 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 ##
  
  `cf push` requires an application name, which you provide either in a manifest 
  or at the command line.
  
  As described in [How cf push Finds the Manifest](#find-manifest) above, the 
  command `cf push` works when the `manifest.yml` file is in the current working 
  directory.
  
  If you do not use a manifest, the minimal push command looks like this:
  
  <pre class="terminal">
  cf push my-application-name
  </pre>
  
  <p class="note"><strong>Note</strong>: When you provide an application name at the command line, <code>cf push</code> uses that application name whether or not there is a different application name in the manifest. If the manifest describes multiple applications, you can push a single application by providing its name at the command line; <code>cf</code> does not push the others.
  These behaviors are useful for testing.</p>
  
  ## <a id='find-app'></a>How cf push Finds the Application ##
  