anchor.diff:      <p class="note"><strong>Note</strong>:  This gem includes the <code>rails&#095;serve&#095;static&#095;assets</code> gem that enables your Rails app to run in production with the static assets serving functionality. The <code>rails&#095;serve&#095;static&#095;assets</code> gem does this by automatically modifying the <code>config.serve&#095;static&#095;assets</code> configuration parameter from <code>false</code> to <code>true</code>. Do not change the value for this option. For more information, refer to the <a href="https://github.com/heroku/rails_12factor">Rails_12factor GitHub README</a>.</p>
   
   1. Run `bundle install` to update your Gemfile.
  +
  +<p class="tip"><strong>Sample App Step</strong><br />You can skip this step. This gem is already included in the <code>rails_sample_app</code> Gemfile.</p>
   
   ### Step 2: (Optional) Configure Automatically Invoked Rake Tasks for Deployed Applications ###
   
  
positive.code: 
  <%=vars.GSG_intro_sentence%>
  
  This guide is intended to walk you through deploying a Ruby on Rails (RoR) app to <%=vars.product_full%>. You can choose whether to push a sample app, your own app, or both.
  
  If at any time you experience a problem following the steps below, try checking the <%=vars.known_issues%> topic, or refer to the [Troubleshooting Application Deployment and Health](./../../devguide/deploy-apps/troubleshoot-app-health.html) topic for more tips.
  
  
  ## <a id='deploy-yourapp'></a>Deploy Your RoR Application ##
  
  This section describes how to deploy your RoR application to <%=vars.product_short%>.
  
  ### Prerequisites ###
  
  * [Bundler](http://bundler.io) configured on your workstation
  - (**Optional**) [Git](http://git-scm.com) configured on your workstation and a [GitHub](https://github.com) account
  * Intermediate to advanced RoR knowledge
  - (**Optional**) Robust production web server for Ruby and RoR apps, such as Unicorn
  * Your Rails 4.x app that runs locally on your workstation
  
  ### Step 1: Add the rails_12factor Gem to Your Gemfile ###
  
  
negative.code: $ cf bind-service my-rails-app rails-postgres
  </pre>
  
  Alternately, you can configure the deployment manifest file by adding a `services` block to the `applications` block and specifying the service instance. For more information and an example on service binding using a manifest, see the next step.
  
  <%=vars.dev_console_5%>
  
  <p class="tip"><strong>Sample App Step</strong><br />You can skip this step. The manifest for the sample app contains a <code>services</code> subblock in the <code>applications</code>block. This binds the <code>rails-postgres</code> service instance you created in the previous step.</p>
  
  ### Step 4: Configure the Manifest File  ###
  
  You can specify app deployment options in a manifest that the `cf push` command uses. For more information about application manifests and supported attributes, refer to the [Deploying with Application Manifests](./../../devguide/deploy-apps/manifest.html) topic.
  
  <p class="tip"><strong>Sample App Step</strong><br />You can skip this step. You can open the <code>manifest.yml</code> file in a text editor to view the bound service instance information. Locate the file in the app root directory and search for the <code>services</code> subblock in the <code>applications</code> block, as the example shows.
  
  <pre class="code">
  ---
  applications:
  ...
    services:
      - rails-postgres
  </pre>
  
  </p>
  
  
  ### 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%>
  
    <p class="tip"><strong>Sample App Step</strong><br />You must do this step to run the sample app.</p>
  
  
  ### Step 6: (Optional) Configure a Production Server  ###
  