anchor.diff:      <pre class="code">
       web: bundle exec puma -e $RAILS_ENV -p 1234 -S ~/puma -C config/puma.rb
       </pre>
  -
  -### 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%>`.
  -
  - * Searches for an application manifest YAML file. A manifest specifies what `cf push` should do with the app.
  - * Determines the appropriate buildpack for the app. A buildpack provides framework and runtime support for your app.
  -
  -<p class="note"><strong>Note</strong>: You must use the CLI to deploy apps.</p>
  -
  -For example: `cf push my-app` creates the URL `my-app.<%=vars.app_domain%>`.
  -
  -1. `cd` to the app directory that you want to deploy.
  -1. Run `cf push [APP-NAME]`.
  -
  -    The URL for your app must be unique from other apps that <%=vars.product_short%> hosts or the push will fail. You can use the following options to create a unique URL:
  -    * `-n` to assign a different HOST name for the app.
  -    * `--random-route` to create a URL that includes the app name and random words.
  -    * Run `cf help push` to view other options for this command.
  -
  -1. Launch a new terminal window and run `cf logs [APP-NAME]` to simultaneously view log activity while the app deploys.
  -1. Browse to your app URL.
  -
  -    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...
  -    OK
  -
  -    requested state: started
  -    instances: 1/1
  -    usage: 256M x 1 instances
  -    urls: jmt0814-rails.<%=vars.app_domain%>
  -
  -
  -         state     since                    cpu    memory        disk
  -    #0   running   2014-08-13 02:45:51 PM   0.0%   69M of 256M   72.7M of 1G
  -    </pre>
  -
  -## <a id='deploy-sample'></a>Deploy a RoR Sample Application ##
  -
  -This section describes how to deploy a RoR sample application named `rails_sample_app`.
  -
  -To learn how to deploy your own RoR app, see [Deploy Your RoR Application](#deploy-yourapp).
  -
  -### Prerequisites ###
  -
  -* [Git](http://git-scm.com) configured on your workstation and a [GitHub](https://github.com) account
  -* Basic RoR knowledge
  -
  -### Step 1: Get a Sample RoR App from GitHub ###
  -
  -Run `git clone https://github.com/cloudfoundry-samples/rails_sample_app` to clone `rails_sample_app` from GitHub.
  -
  -### Step 2: 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%>.
  -
  -### Step 3: Deploy the Sample App ###
  -
  -1. `cd` to the cloned app directory.
  -1. Run `cf create-service elephantsql turtle rails-postgres`.
  -1. Run `cf push rails_sample_app -n [HOST_NAME]`.
  -
  -Example: `cf push rails_sample_app -n jc0825-rails`
  -
  -`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.
  -
  -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.
  +	
  +<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%>`.
  +
  +The URL for your app must be unique from other apps that <%=vars.product_short%> hosts or the push will fail. Use the following options to help create a unique URL:
  +
  +* `-n` to assign a different HOST name for the app.
  +* `--random-route` to create a URL that includes the app name and random words.
  +* Run `cf help push` to view other options for this command.
  +
  +If you want to view log activity while the app deploys, launch a new terminal window and run `cf logs [APP-NAME]`.
  +
  +Once your app deploys, browse to your app URL. 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.
  +
  +<p class="tip"><strong>Sample App Step</strong><br />
  +Run <code>cf push rails_sample_app -n [HOST_NAME]</code>.
  +<br /><br />
  +Example: <code>cf push rails_sample_app -n jc0825-rails</code>
  +<br /><br />
  +The example below shows the terminal output of deploying the <code>rails_sample_app</code>. <code>cf push</code> uses the instructions in the manifest file to create the app, create and bind the route, and upload the app. It then binds the app to the <code>rails-postgres</code> service 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.
  +</p>
   
   <pre class="terminal">
   
  
positive.code:     on\_worker\_boot do
        # things workers do
      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. 
  
  
negative.code: 
  Common reasons deploying an app fails include:
  
  * 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 ###
  