anchor.diff:  <tr>
   </table>
   
  -###<a id='random-route'></a>The random-route attribute ###
  -
  -Use the `random-route` attribute to create a URL that includes the app name and
  -random words.
  -Use this attribute to avoid URL collision when pushing the same app to multiple spaces, or to avoid managing app URLs.
  -
  -The command line option that corresponds to this attribute is `--random-route`.
  -
  -<pre>
  ----
  -  ...
  -  random-route: true
  -</pre>
  -
  -
  -###<a id='path'></a>The path attribute
  -
  -You can use the `path` attribute to tell Cloud Foundry the directory location where it can find your application. 
  -
  -The directory specified as the `path`, either as an attribute or as a parameter on the command line, becomes the location where the buildpack `Detect` script executes.
  -
  -The command line option that overrides this attribute is `-p`.
  -
  -<pre>
  ----
  -  ...
  -  path: /path/to/application/bits
  -</pre>
  -
  -For more information, see the [How cf push Finds the Application](#find-app) topic.
  -
  -###<a id='timeout'></a>The timeout attribute ###
  +###<a id='stack'></a>stack ###
  +
  +Use the `stack` attribute to specify which stack to deploy your application to.
  +
  +To see a list of available stacks, run `cf stacks` from the cf cli.
  +
  +<pre>
  +---
  +  ...
  +  stack: cflinuxfs2
  +</pre>
  +
  +The command line option that overrides this attribute is `-s`.
  +
  +###<a id='timeout'></a>timeout ###
   
   The `timeout` attribute defines the number of seconds that Cloud Foundry allocates for starting your application.
   
  
positive.code: 
  The command line option that overrides the timeout attribute is `-t`.
  
  ###<a id='no-route'></a>The no-route attribute ###
  
  By default, `cf push` assigns a route to every app. But, some apps process data while running in the background and should not be assigned routes.
  
  You can use the `no-route` attribute with a value of `true` to prevent a route from being created for your app.
  
  <pre>
  ---
    ...
    no-route: true
  </pre>
  The command line option that corresponds to this attribute is `--no-route`.
  
  In the newer Diego architecture, `no-route` skips creating and binding a route for the app, but does not specify which type of health check to perform. If your app does not listen on a port because it is a worker or a scheduler app, then it does not satisfy the port-based health check and Cloud Foundry marks it as crashed. To prevent this, disable the port-based health check with `cf set-health-check APP_NAME none`.
  
  In the older Droplet Execution Agent (DEA) architecture, `cf set-health-check APP_NAME none` is unnecessary because `no-route` causes the DEAs to skip the port health-check on app startup.
  
  To remove a route from an existing app, perform the following steps:
  
  1. Remove the route using the `cf unmap-route` command.
  1. Push the app again with the `no-route: true` attribute in the manifest or the `--no-route` command line option.
  
  For more information, see [Describing Multiple Applications with One Manifest](#multi-apps) below.
  
  ###<a id='env-block'></a>Environment Variables ###
  
  The `env` block consists of a heading, then one or more environment variable/value pairs.
  
  
negative.code: 
  The command line option that overrides this attribute is `-d`.
  
  ###<a id='health-check-http-endpoint'></a>health-check-http-endpoint ###
  
  Use the `health-check-http-endpoint` attribute to customize the endpoint for the `http` health check type. If you do not provide a `health-check-http-endpoint` attribute, 
  it uses endpoint '/'.
  
  <pre>
  ---
    ...
    health-check-type: http
    health-check-http-endpoint: /health
  </pre>
  
  ###<a id='health-check-type'></a>health-check-type ###
  
  Use the `health-check-type` attribute to set the `health_check_type` flag to either `port`, `process` or `http`. If you do not provide a `health-check-type` attribute, 
  it defaults to `port`.
  