anchor.diff:  
   ## <a id='troubleshoot-push'></a>Step 7: Troubleshoot Deployment Problems ##
   
  -If your application does not start on Cloud Foundry, first ensure that your 
  -application can run locally. 
  +If your application does not start on Cloud Foundry, first ensure that your
  +application can run locally.
   
   You can troubleshoot your application in the cloud using the `cf` CLI.
   See [Troubleshoot Application Deployment and Health](./troubleshoot-app-health.html).
positive.code: 
  Before you can push your application to Cloud Foundry you need to know:
  
  * The API endpoint for your Cloud Foundry instance. Also known as the target 
  URL, this is <%=vars.api_endpoint%>.
  * Your username and password for your Cloud Foundry instance.
  * The organization and space where you want to deploy your application.
  
negative.code: 
  For more information about the manifest file, see the [Deploying with Application Manifests](./manifest.html) topic.
  
  ### Configure the Initial Environment for Your Applications ###
  
  Each application deployed to Cloud Foundry runs within its own self-contained
  environment, a Linux [Warden](../../concepts/architecture/warden.html)
  container.
  During startup, the container runs a [bash](https://www.gnu.org/software/bash/bash.html) shell that executes any
  scripts found in the `.profile.d` directory.
  To configure the initial environment for your applications, you must do the
  following:
  
  1. Create a `.profile.d` directory under the build directory of your
  application.
  1. Add shell scripts to the `.profile.d` directory. These shell scripts must be
  executable by bash, and must have a `.sh` extension.
  
  For example, set the [MEMORY_LIMIT](./environment-variable.html#memory)
  environment variable to 512 MB by creating a shell script, with the following
  content, within the `profile.d` directory:
  
  ```
  export MEMORY_LIMIT=512M;
  ```
  
  ## <a id='push'></a>Step 5: Push the Application ##
  
  Run the following command to deploy an application without a manifest:
  
    `cf push APP-NAME`
  
  If you provide the application name in a manifest, you can reduce the command to
  `cf push`.
  See [Deploying with Application Manifests](./manifest.html).
  
  