anchor.diff:  
   <pre class="terminal">
   $ cf create-route my-space <%=vars.app_domain%> --hostname store --path products
  +Creating route store.<%=vars.app_domain%>/products for org my-org / space my-space as username<span>@</span>example.com...
  +OK
  +
   $ cf create-route my-space <%=vars.app_domain%> --hostname store --path orders
  +Creating route store.<%=vars.app_domain%>/orders for org my-org / space my-space as username<span>@</span>example.com...
  +OK
  +
   $ cf create-route my-space <%=vars.app_domain%> --hostname store
  +Creating route store.<%=vars.app_domain%> for org my-org / space my-space as username<span>@</span>example.com...
  +OK
  +
   </pre>
   
   The developer can then map the the new routes to different apps by following the steps in the <a href="#map-route">Map a Route to your Application</a> section below.
  
positive.code: 
  ### <a id='map-route'></a>Map a Route to your Application ###
  
  For an app to receive requests to a route, developers must map the route to the app with the `cf map-route` command. If the route does not already exist, this command creates it.
  
  Developers can create and reserve routes for later use by following the steps in the <a href="#map-route-manually">Manually Map a Route</a> section. Or they can map routes to their app immediately as part of a push by following the steps in the <a href="#map-route-on-push">Map a Route with Application Push</a> section.
  
  
negative.code: 
  <pre class="terminal">
  $ cf create-route my-space foo.<%=vars.private_app_domain%>
  Creating route foo.<%=vars.private_app_domain%> for org my-org / space my-space as username<span>@</span>example.com...
  OK
  
  </pre>
  
  Assuming DNS has been configured for this subdomain, this command instructs <%=vars.product_short%> to route requests to apps mapped to this route from the following URLs: 
  