anchor.diff:  #0   running   2016-06-08 04:44:07 PM   0.0%   0 of 1G   0 of 1G
   </pre>
   
  -For more information about available buildpacks, see the <a href="https://docs.cloudfoundry.org/buildpacks/">Buildpacks</a> topic.
  -
  -### <a id='name'></a> Always Provide an App Name to cf push
  -
  -`cf push` requires an app name, which you provide either in a manifest
  -or at the command line.
  -
  -`cf push` locates the `manifest.yml` in the current working
  -directory by default, or in the path provided by the `-f` option.
  -
  -If you do not use a manifest, the minimal `cf push` command looks like this:
  -
  -<pre class="terminal">
  -$ cf push my-app
  -</pre>
  -
  -<p class="note"><strong>Note</strong>: When you provide an app name at the command line, <code>cf push</code> uses that app name whether or not there is a different app name in the manifest. If the manifest describes multiple apps, you can push a single app by providing its name at the command line; the cf CLI does not push the others.
  -Use these behaviors for testing.</p>
  -
  -
  -### <a id='find-app'></a> How cf push Finds the App
  -
  -By default, `cf push` recursively pushes the contents of the current working directory. Alternatively, you can provide a path using either a manifest or a command line option.
  -
  -- If the path is to a directory, `cf push` recursively pushes the contents of that directory instead of the current working directory.
  -- If the path is to a file, `cf push` pushes only that file.
  -
  -<p class="note"><strong>Note</strong>: If you want to push more than a single file, but not the entire contents of a directory, consider using a <code>.cfignore</code> file to tell <code>cf push</code> what to exclude.</p>
  -
  -## <a id='user-provided'></a> User-Provided Service Instances ##
  -
  -To create or update a user-provided service instance, you need to supply basic parameters. For example a database service might require a username, password, host, port, and database name.
  -
  -The cf CLI has three ways of supplying these parameters to create or update an instance of a service: interactively, non-interactively, and in conjunction with 
  -third-party log management software as described in [RFC 6587](http://tools.ietf.org/html/rfc6587). When used with third-party logging, the cf CLI sends data formatted according to [RFC 5424](http://tools.ietf.org/html/rfc5424).
  -
  -You create a service instance with `cf cups` and update one with `cf uups` as described below. 
  -
  -### <a id='user-cups'></a>The cf create-user-provided-service (cups) Command ###
  +
  +### <a id='new-route'></a> Map a Route to an App
  +
  +For information about mapping a different route to your app, see [Routes and Domains](https://docs.cloudfoundry.org/devguide/deploy-apps/routes-domains.html). 
  +
  +If you do not provide a hostname (also known as subdomain), `cf push` routes your app to a URL of the form `APPNAME.DOMAIN` based on the name of your app and your default domain. 
  +
  +
  +## <a id='user-provided'></a> Create or Update User-Provided Service Instances ##
  +
  +To create or update a user-provided service instance, you need to supply basic parameters. For example, a database service might require a username, password, host, port, and database name.
  +
  +You can provide these parameters in the following ways using the cf CLI: 
  +
  +* Interactively 
  +* Non-interactively 
  +* With third-party log management software as described in [RFC 6587](http://tools.ietf.org/html/rfc6587). When used with third-party logging, the cf CLI sends data formatted according to [RFC 5424](http://tools.ietf.org/html/rfc5424).
  +
  +### <a id='user-cups'></a>Create a Service Instance ###
   
   Use [cf create-user-provided-service](http://cli.cloudfoundry.org/en-US/cf/create-user-provided-service.html) (alias `cf cups`) creates a new service instance.
   
  
positive.code:   louie<span>@</span>example.com
  </pre>
  
  ### <a id='managing-roles'></a>Commands for Managing Roles ###
  
  These commands require <%=vars.product_short%> admin permissions and take username, org or space, and role as arguments:
  
  * [cf set-org-role](http://cli.cloudfoundry.org/en-US/cf/set-org-role.html)
  
  * [cf unset-org-role](http://cli.cloudfoundry.org/en-US/cf/unset-org-role.html)
  
  * [cf set-space-role](http://cli.cloudfoundry.org/en-US/cf/set-space-role.html)
  
  * [cf unset-space-role](http://cli.cloudfoundry.org/en-US/cf/unset-space-role.html)
  
  Available roles are `OrgManager`, `BillingManager`, `OrgAuditor`, `SpaceManager`, `SpaceDeveloper`, and `SpaceAuditor`. For example, to grant the Org Manager role to a user within an org:
  
  <pre class="terminal">
  $ cf set-org-role huey@example.com example-org OrgManager
  
negative.code: * `ORG`: The org where you want to deploy your apps.
  * `SPACE`: The space in the org where you want to deploy your apps.
  
  <pre class="terminal">
  $ cf login -a https://api.example.com -u username<span>@</span>example.com
  API endpoint: https://api.example.com
  