anchor.diff:  `TMPDIR=/home/vcap/tmp`
   
   ### <a id='USER'></a>USER###
  -The user account under which the DEA runs.
  +The user account under which the application runs.
   
   `USER=vcap`
   
   ### <a id='VCAP-APP-HOST'></a>VCAP\_APP\_HOST
   
  -The IP address of the DEA host.
  +The IP address of the host. Deprecated: the DEAs set this to be `0.0.0.0`,
  +and Diego Cells do not provide this environment variable.
   
   `VCAP_APP_HOST=0.0.0.0`
  +
  +
  +### <a id='VCAP-APP-PORT'></a>VCAP\_APP\_PORT ###
  +
  +Deprecated name for the [PORT](#PORT) variable defined above.
  +
   
   ### <a id='VCAP-APPLICATION'></a>VCAP_APPLICATION ###
   
  
positive.code:   </tr>
    <tr>
      <td><code>instance_index</code></td>
      <td>Index number of the instance. You can access this value directly with the <a href="#CF-INSTANCE-INDEX">CF_INSTANCE_INDEX</a> variable.</td>
    </tr>
    <tr>
      <td><code>limits</code></td>
      <td>The memory, disk, and number of files permitted to the instance. Memory and disk limits are supplied when the application is deployed, either on the command line or in the application manifest. The number of files allowed is operator-defined.</td>
    </tr>
    <tr>
      <td><code>port</code></td>
      <td>Port of the application instance. You can access this value directly with the <a href="#PORT">PORT</a> variable.</td>
    </tr>
    <tr>
      <td><code>started_at</code> or <code>start</code></td>
      <td>The last time the application was started.</td>
    </tr>
    <tr>
      <td><code>started_at_timestamp</code></td>
      <td>Timestamp for the last time the application was started.</td>
    </tr>
    <tr>
      <td><code>state_timestamp</code></td>
      <td>The timestamp for the time at which the application achieved its current state.</td>
    </tr>
  </table>
  
  
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.
  
  