anchor.diff:  
   Use the `cf env` command to view the Cloud Foundry environment variables for your application. `cf env` displays the following environment variables:
   
  -* The `VCAP_SERVICES` variables existing in the container environment
  +* The `VCAP_APPLICATION` and `VCAP_SERVICES` variables provided in the container environment
   * The user-provided variables set using the `cf set-env` command
   
   <pre class="terminal">
  
positive.code: 
  Environment variables are the means by which the Cloud Foundry runtime
  communicates with a deployed application about its environment.
  This page describes the environment variables that Droplet Execution Agents
  (DEAs) and buildpacks set for applications.
  
  For information about setting your own application-specific environment
  variables, refer to the [Set Environment Variable in a Manifest](./manifest.html#env-block) section in
  
negative.code: [Node.js](../../buildpacks/node/node-tips.html#env-var), and
  [Ruby](../../buildpacks/ruby/ruby-tips.html#env-var).
  
  ### <a id='CF-INSTANCE-ADDR'></a>CF\_INSTANCE\_ADDR ###
  The [CF\_INSTANCE\_IP](#CF-INSTANCE-IP) and [CF\_INSTANCE\_PORT](#CF-INSTANCE-PORT) of the app instance in the format `IP:PORT`.
  
  `CF_INSTANCE_ADDR=1.2.3.4:5678`
  
  ### <a id='CF-INSTANCE-GUID'></a>CF\_INSTANCE\_GUID ###
  The GUID of the application. Available only to instances on Diego cells.
  
  `CF_INSTANCE_GUID=41653aa4-3a3a-486a-4431-ef258b39f042`
  
  ### <a id='CF-INSTANCE-INDEX'></a>CF\_INSTANCE\_INDEX ###
  The index number of the app instance.
  
  `CF_INSTANCE_INDEX=0`
  
  ### <a id='CF-INSTANCE-IP'></a>CF\_INSTANCE\_IP ###
  The external IP address of the host running the app instance.
  
  `CF_INSTANCE_IP=1.2.3.4`
  
  ### <a id='CF-INSTANCE-PORT'></a>CF\_INSTANCE\_PORT ###
  Same as the [PORT](#PORT) of the app instance.
  
  `CF_INSTANCE_PORT=5678`
  
  ### <a id='CF-INSTANCE-PORTS'></a>CF\_INSTANCE\_PORTS ###
  
  The list of mappings between internal (container-side) and external
  (host-side) ports allocated to the instance's container.
  Note that not all of the internal ports are necessarily available for the
  application to bind to, as some of them may be used by system-provided
  services that also run inside the container.
  On the DEAs, these internal and external values will be the same, but on Diego
  cells, they may differ.
  
  `CF_INSTANCE_PORTS=[{external:61045,internal:5678},{external:61046,internal:2222}]`
  
  
  ### <a id='HOME'></a>HOME ###
  Root folder for the deployed application.
  
  