anchor.diff:  
     `cf push [APP_NAME]` pushes the specified app from the current directory to <%=vars.product_short%>. Use the `-n` flag to create a unique host name for the app to avoid URL collisions with other apps.
   
  -  `cf push` automatically searches for an [application manifest YAML file](./../../devguide/deploy-apps/manifest.html) (`manifest.yml`) and also determines the appropriate [buildpack](./index.html) for the app.  A manifest specifies what `cf push` should do with the app and the buildpack provides framework and runtime support for your app. 
  +  `cf push` automatically searches for an [application manifest YAML file](./../../devguide/deploy-apps/manifest.html) (`manifest.yml`) and also determines the appropriate [buildpack](./index.html) for the app.  A manifest specifies what `cf push` should do with the app and the buildpack provides framework and runtime support for your app.
   
     The example shows the terminal output of deploying the `rails_sample_app`. `cf push` uses the instructions in the manifest file to create the app, create and bind and the route, and upload the app to <%=vars.product_short%>. It then binds the app to the `rails-postgres` service you defined in the previous step, and follows the instructions in the manifest to start one instance of the app with 256M. After the app starts, the output displays the health and status of the app.
   
  
positive.code: 
  You can also bind a service using the <%=vars.dev_console_2%>.
  
  ### <a id='yourapp-step5'></a>Step 5: Log in and Target the API Endpoint   ###
  Run `cf login -a [API_ENDPOINT]`, enter your login credentials, and select a space and org. The API endpoint is <%=vars.api_endpoint%>.
  
  <%=vars.gen_GSG%> 
  
  
  ### <a id='yourapp-step6'></a>Step 6: (Optional) Configure a Production Server  ###
  
  <%=vars.product_short%> uses the default Ruby web server library WEBrick for Ruby and RoR apps. However, <%=vars.product_short%> can support a more robust production web server, such as Phusion Passenger, Puma, Thin, or Unicorn. To set a different production web server for your app:
  
  1. Modify your app to use the production web server.
  1. Configure the `web` setting in a Procfile to point to the production web server. 
  
  When you deploy, `cf push` detects that your app requires the Cloud Foundry Ruby [buildpack](./index.html), and that buildpack uses the modified Procfile to configure your app with the changed production web server settings. For an example of how to configure an application and a Procfile to use a different web server, refer to the [Heroku Deploying Rails Applications with Unicorn](https://devcenter.heroku.com/articles/rails-unicorn) topic.
  
  ### <a id='yourapp-step7'></a>Step 7: Deploy Your Application ###
  When you deploy your application, `cf push`:
  
   * Creates a URL that is the route to your application. The URL is in the form HOST.DOMAIN, where HOST is the APP_NAME and DOMAIN is specified by your administrator. Your DOMAIN is`<%=vars.app_domain%>`.
  
negative.code:     Search for the `urls` field in the `App started` block in the output of the `cf push` command. Use the URL to access your app online.
  
      <pre class="terminal">
  
      App started
  
      Showing health and status for app rails_sample_app in org Cloud-Apps / space development as clouduser@example.com...
  