anchor.diff:  
   <p class="note"><strong>Note</strong>: If you want to push more than a single file, but not the entire contents of a directory, consider using a <code>.cfignore</code> file to tell <code>cf push</code> what to exclude.</p>
   
  -## <a id='precedence'></a>Precedence Between Manifests, Command line Options, and Most Recent Values ##
  +## <a id='precedence'></a>Precedence Between Manifests, Command Line Options, and Most Recent Values ##
   
   When you push an application for the first time, Cloud Foundry applies default values to any attributes that you do not set in a manifest or `cf push` command line options.
   
  
positive.code: title: Deploying with Application Manifests
  ---
  
  _This page assumes you are using cf CLI v6._
  
  Application manifests tell `cf push` what to do with applications. This includes everything from how many instances to create and how much memory to allocate to what services applications should use.
  
  A manifest can help you automate deployment, especially of multiple applications at once.
  
  ##<a id='find-manifest'></a>How cf push Finds the Manifest ##
  
  
negative.code:   ...
    env:
      RAILS_ENV: production
      RACK_ENV: production 
  </pre>
  
  `cf push` deploys the application to a container on the server. The variables belong to the container environment.
  