anchor.diff:  
   <%=vars.GSG_intro_sentence%>
   
  -This guide is intended to walk you through deploying a Ratpack framework app to <%=vars.product_full%>. 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.
  +This guide is intended to walk you through deploying a Ratpack app to <%=vars.product_full%>. If you experience a problem following the steps below,  check the <%=vars.known_issues%> topic or refer to the [Troubleshooting Application Deployment and Health](./../../devguide/deploy-apps/troubleshoot-app-health.html) topic.
   
   <p class="tip"><strong>Sample App Step</strong><br />If you want to go through this tutorial using the sample app, run <code>git clone git@github.com:camelpunch/pong_matcher_groovy.git</code> to clone the <code>pong_matcher_groovy</code> app from GitHub, and follow the instructions in the Sample App Step boxes.</p>
   
  +<p class="note"><strong>Note</strong>: Ensure that your Ratpack app runs locally before continuing with this procedure.</p>
  +
   ## <a id='deploy-yourapp'></a>Deploy a Ratpack Application ##
   
   This section describes how to deploy a Ratpack application to <%=vars.product_short%>.
  
positive.code: 
    <p class="tip"><strong>Sample App Step</strong><br />You must do this step to run the sample app.</p>
  
  
  ### Step 9: Deploy Your Application ###
  
  <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] -p [PATH-TO-.distZip]` to deploy your application. 
  
  <p class="note"><strong>Note</strong>: You must deploy the <code>.distZip</code> artifact for a Ratpack app, and you must include the path to the <code>.distZip</code> file in the `cf push` command if you do not declare the path in the `applications` block of the manifest file. For more information, refer to the <a href="./java-tips.html">Tips for Java Developers</a> topic.</p>
  
  `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 />
  <ol>
  <li>Build the app. Change to the <code>app</code>directory, and run <code>./gradlew distZip</code>.</li>
  <li>Push the app. Run <code>cf push pong_matcher_groovy -n [HOST_NAME]</code>.
  <br /><br />
  Example: <code>cf push pong_matcher_groovy -n groovy-ratpack-app</code>
  <p class="note"><strong>Note</strong>: You do not have to include the <code>-p</code> flag when you deploy the sample app. The sample app manifest declares the path to the archive that <code>cf push</code> uses to upload the app files.</p>
  </li>
  </ol>
  
  The example below shows the terminal output of deploying the <code>pong_matcher_groovy</code> app. <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>baby-redis</code> service and follows the instructions in the manifest to start one instance of the app with 512 MB. After the app starts, the output displays the health and status of the app.
  </p>
  
  <pre class="terminal">
  
  
negative.code: 
  For more information, refer to the [Build Tool Integration](./build-tool-int.html) topic.
  
  <p class="tip"><strong>Sample App Step</strong><br />You can skip this step. The <code>pong_matcher_groovy</code> sample app includes a <code>build.gradle</code> file.</p>
  
  ### Step 3: Declare App Dependencies  ###
  
  Declare all the dependency tasks for your app in the build script of your chosen build tool. The table lists build script information for Gradle and Maven and provides documentation links for each build tool.
  
  <table border="1" class="nice">
  <tr>
  