Bug 971208

https://access.redhat.com/site/documentation/en-US/OpenShift/2.0/html/User_Guide/sect-OpenShift-User_Guide-Environment_Variables.html#sect-OpenShift-User_Guide-Environment_Variables-Informational_Environment_Variables

and also 

https://www.openshift.com/page/openshift-environment-variables

Suggested rewording: 

"These variables provide environment information for your application. Your application can read these environment variables and use the information to configure itself for the OpenShift environment."

Table 7.2. Informational Environment Variables

Environment Variable Name	 Example	 Purpose
OPENSHIFT_APP_DNS	 appname-namespace.example.com	 The application's fully-qualified domain name
OPENSHIFT_APP_NAME	 appname	 The application's name
OPENSHIFT_APP_UUID	 0123456789abcdef0123456789abcdef	 The UUID of the application (32 hex characters)
OPENSHIFT_INTERNAL_IP	 127.0.250.1	 The IP address the application listens on
OPENSHIFT_INTERNAL_PORT	 8080	 The port the application receives requests from

In my node.js app the OPENSHIFT_INTERNAL_IP and OPENSHIFT_INTERNAL_PORT are not available in the environment.

Instead, I need to use the following environment variables:

OPENSHIFT_NODEJS_IP    Purpose: The IP address for a node application
OPENSHIFT_NODEJS_PORT    Purpose: The IP port for a node application

example usage is like this:

// Default to 127.0.0.1 and 8080 for local testing, when the app is not running on OpenShift
myApp.IPAddress = process.env.OPENSHIFT_NODEJS_IP || '127.0.0.1';
myApp.IPPort = process.env.OPENSHIFT_NODEJS_PORT || 8080;

In this case it's obvious when the NODEJS_IP and _PORT variables are available - when you are using a node.js gear. However, when are the OPENSHIFT_INTERNAL_IP and _PORT variables available? That should probably be made explicit, so that peeps know when to, and when not to rely on their existence.