anchor.diff:  
   ### Step 5: Verifying the app ###
   
  -You can verify the sample app you have pushed by browsing to the URL generated in the output of the previous step. In this example, the url is `urls: jmt2014-rails.<%=vars.app_domain%>`.
  +You can verify the sample app you have pushed by browsing to the URL generated in the output of the previous step. In this example, the url is `urls: my-app.<%=vars.app_domain%>`.
   
   
   You've now pushed an app to <%=vars.product_short%>! For help deploying your own app, visit the **Deploy Your App: Guides by Framework** section of the help.
  
positive.code: 		requested state: started
  		instances: 1/1
  		usage: 256M x 1 instances
  		urls: jmt2014-rails.<%=vars.app_domain%>
  
  		     state     since                    cpu    memory          disk
  		#0   running   2014-08-25 03:32:10 PM   0.0%   68.4M of 256M   73.4M of 1G
  
negative.code: ---
  title: Deploy a Sample Ruby on Rails Application
  ---
  
  This topic walks the reader through the process of deploying a sample Ruby on Rails app to <%= vars.product_full %>. 
  
  The take aways should be:
  
  - Using the CF CLI to target a CF deployment.
  - Familiarity with app deployment manifests.
  - Deploying first APP.
  - Familiarity with how app URL endpoints are generated in CF.
  - Adding a service instance (A postrgres database, in this example).
  
  
  ## Prerequisites
  
  - A working CF deployment. See [Deploying CF Using Bosh Lite](http://docs.cloudfoundry.org/deploying/boshlite/deploy_cf_boshlite.html).
  - [Cloud Foundry CLI](http://docs.cloudfoundry.org/devguide/installcf/install-go-cli.html)
  - Username and password with **Space Developer** permissions. See [Roles and Permissions](../../concepts/roles.html#space-roles).
  
  This guide walks you through deploying a sample Ruby on Rails app to <%=vars.product_short%>. Follow this guide to get started with <%=vars.product_short%> and experience the deploy process from start to finish.
  
  ### Step 1: Clone the App ###
  
  Run the following in the terminal to clone the `rails_sample_app` from GitHub:
  <pre class='terminal'>
  	git clone https://github.com/cloudfoundry-samples/rails_sample_app
  </pre>
  
  Change into the rails\_sample\_app directory and examine its contents. The release contains a very simple Ruby on Rails app with the single addition of the application manifest `manifest.yml`, which allows CF to deploy the app. For more about application manifests, see [Deploying with Application Manifests](https://docs.cloudfoundry.org/devguide/deploy-apps/manifest.html#minimal-manifest).
  
  <pre class='terminal'>
  ~/workspace/rails_sample_app $ ls
  Gemfile	README.markdown	app	bin	config db files <div style='display:inline;color:black;background:yellow'>manifest.yml</div> script vendor
  Gemfile.lock	Rakefile autotest bundler_stubs config.ru doc lib public spec
  </pre>
  
  ### Step 2: Log in and Target the API Endpoint ###
  
  Run the following to log in and target the API endpoint of your Cloud Foundry deployment. You will be prompted for login credentials, and to select a space and org. <br><br> For `YOUR-API-ENDPOINT`, enter the IP of the BOSH director for your Cloud Foundry deployment. The IP must entered in the following format: `http://api.IP-ADDRESS`
  <pre class='terminal'>cf login -a YOUR-API-ENDPOINT</pre>
  
  For more information about Spaces and Orgs, see [Orgs, Spaces, Roles, and Permissions](../../concepts/roles.html). 
  
  
  ### Step 3: Create a Service Instance for our Application Database ###
  
  In Cloud Foundry, a database is considered a type of service. To add a database for our sample application we will create an instance of [elephantsql](http://www.elephantsql.com/), a third party database as a service provider.
  
  Run the following terminal command to creates a postgresql service instance for our app. 
  
    <pre class="terminal">
    $   cf create-service elephantsql turtle rails-postgres
  