anchor.diff:      end
   </pre>
   
  -1. In the root directory of your app, create a Procfile and add a command line for a `web` process type that points to your web server. 
  +1. In the root directory of your app, create a Procfile and add a command line for a `web` process type that points to your web server.
   
       The example below shows a command that starts a Puma web server and specifies the app runtime environment, TCP port, and paths to the server state information and configuration files.
       Refer to your web server documentation for how to configure the specific command for a process type.
  
positive.code:     <pre class="code">
      web: bundle exec puma -e $RAILS_ENV -p 1234 -S ~/puma -C config/puma.rb
      </pre>
  	
  <p class="tip"><strong>Sample App Step</strong><br />You can skip this step. The <code>rails_sample_app</code> does not require a production server.</p>	
  
  ### Step 7: Deploy an App ###
  
  <p class="note"><strong>Note</strong>: You must use the cf CLI to deploy apps.</p>
  
  From the root directory of your application, run `cf push [APP-NAME]` to deploy your application. 
  
  `cf push [APP-NAME]` creates a URL route to your application in the form HOST.DOMAIN, where HOST is your [APP-NAME] and DOMAIN is specified by your administrator. Your DOMAIN is`<%=vars.app_domain%>`. For example: `cf push my-app` creates the URL `my-app.<%=vars.app_domain%>`.
  
  
negative.code: 
  ### Step 8: Test a Deployed App ###
  
  You’ve deployed an app to <%=vars.product_short%>!
  
  Use the `cf` <%=vars.dev_console_2%> to review information and administer your app and your <%=vars.product_short%> account. For example, you could edit the `manifest.yml` to increase the number of app instances from 1 to 3, and redeploy the app with a new app name and host name.
  
  