anchor.diff:  
   If you do not see a buildpack for your app, you may still be able to push your application with a [custom buildpack](../../buildpacks/custom.html) using `cf push -b` with a path to your buildpack.
   
  -### App Deploy Fails ###
  +### <a id='deploy_fail'></a> App Deploy Fails ###
   Even when the deploy fails, the app might exist on <%=vars.product_short%>.
   Run `cf apps` to review the apps in the currently targeted org and space. You might be able to correct the issue using the <%=vars.dev_console_2%>, or you might have to delete the app and redeploy.
   
  
positive.code: * You did not successfully create and bind a needed service instance to the app, such as a PostgreSQL or MongoDB service instance. Refer to Step 3: Create and Bind a Service Instance for a RoR Application.
  * You did not successfully create a unique URL for the app. Refer to the troubleshooting tip App Requires Unique URL.
  
  ### App Requires Unique URL ###
  <%=vars.product_short%> requires that each app that you deploy has a unique URL. Otherwise, the new app URL collides with an existing app URL and <%=vars.product_short%> cannot successfully deploy the app. You can resolve this issue by running `cf push` with either of the following flags to create a unique URL:
  
  * `-n` to assign a different HOST name for the app.
  
negative.code: 
  If this happens, try the following:
  
    * **Find the reason app is failing and modify your code.**
      Run `cf events APP-NAME` and `cf logs APP-NAME --recent` and look for
  messages similar to this:
    <pre class="terminal">
    2014-04-29T17:52:34.00-0700   app.crash          index: 0, reason: CRASHED,
    exit\_description: app instance exited, exit\_status: 1
    </pre>
    These messages may identify a memory or port issue.
    If they do, take that as a starting point when you re-examine and fix your
  application code.
  
    * **Make sure your application code uses the `PORT` environment variable.**
  Your application may be failing because it is listening on the wrong port.
  Instead of hard coding the port on which your application listens, use the `PORT` environment variable.
      
      For example, this Ruby snippet assigns the port value to the `listen_here`
  variable:
       `listen_here = ENV['PORT']`
     
      For more examples specific to your application framework, see the
  appropriate [buildpacks documentation](../../buildpacks/) for your app's language.
  
    * **Make sure your app adheres to the principles of the
  