anchor.diff:   * Automatically searches for an application manifest YAML file (`manifest.yml`). A manifest specifies what `cf push` should do with the app.
    * Automatically determines the appropriate buildpack for the app. A buildpack provides framework and runtime support for your app.
   
  -<pre class="note"><strong>Note</strong>: You must use the CLI to deploy apps. You cannot use the <a href="./../../console/index.html">Developer Console</a>.</pre>
  +<pre class="note"><strong>Note</strong>: You must use the CLI to deploy apps.</pre>
   
   For example: `cf push my-app` creates the URL `my-app.cfapps.io`.
   
  
positive.code:     - rails-postgres
  </pre>
  
  You can also bind a service using the CLI or the [Developer Console](./../../console/index.html).
  
  ### <a id='yourapp-step5'></a>Step 5: Login to <%=vars.product_short%> and Target the API Endpoint   ###
  Run `cf login -a api.run.pivotal.io`, enter your login credentials, and select a space and org.
  
  For more information, refer to [Step 3: Point Your CLI to <%=vars.product_short%>](./../../starting/index.html#connect-api) of the Getting Started with Pivotal Web Services topic. 
  
  ### <a id='yourapp-step6'></a>Step 6: (Optional) Configure a Production Server  ###
  
  
negative.code: 
  ### <a id='yourapp-step3'></a>Step 3: Configure a Service Instance for Your RoR Application ###
  
  This section describes using the CLI to configure a PostgreSQL managed service instance for your app. <%=vars.dev_console_1%>
  
  <%=vars.product_short%> supports two types of service instances: 
  
  