anchor.diff:  
   Next, push your application to Cloud Foundry and instruct Cloud Foundry to connect to the debugger running on your local machine using the following instructions:
   
  -1. Edit your manifest.yml file. Set the instances count to 1. If you set this greater than one, multiple applications try to connect to your debugger.
  -1. Also in manifest.yml, add the [`env` section](http://docs.cloudfoundry.org/devguide/deploy-apps/manifest.html#env-block) and create a variable called `JAVA_OPTS`.
  -1. Add the remote debugger configuration to the `JAVA_OPTS` variable: `-agentlib:jdwp=transport=dt_socket,address=<your-ip>:<your-port>`.
  -1. Save the manifest.yml file.
  +1. Edit your `manifest.yml` file. Set the instances count to 1. If you set this greater than one, multiple applications try to connect to your debugger.
  +1. Also in `manifest.yml`, add the [`env` section](http://docs.cloudfoundry.org/devguide/deploy-apps/manifest.html#env-block) and create a variable called `JAVA_OPTS`.
  +1. Add the remote debugger configuration to the `JAVA_OPTS` variable: `-agentlib:jdwp=transport=dt_socket,address=YOUR-IP-ADDRESS:YOUR-PORT`.
  +1. Save the `manifest.yml` file.
   1. Run `cf push`.
   
   Upon completion, you should see that your application has started and is now connected to the debugger running in your IDE. You can now add breakpoints and interrogate the application just as you would if it were running locally.
  
positive.code: When you push a Java application, specify the path to the WAR:
  
      <pre class="terminal">
      $ cf push MY-APP -p /Path/To/WAR/file
      </pre>
  
      You can determine whether or not the path was specified for a previously
  
negative.code: 
  <pre class="terminal">
  $ gradle build
  $ cf push my-application -p build/libs/my-application-version.jar
  </pre>
  
  ## <a id='play-framework'></a>Play Framework ##
  