At runtime Apcera exposes and populates various environment variables for jobs, packages, and services.
||Root folder for the deployed application.|
||system path used to search for executables.|
||Port the app binds to. It can be specified on the route, else it is randomly chosen.|
||IP address of the host of the isolation context.|
||hostip:port - hostip is the IP address of the host of the isolation context.|
||Name of the process from the Job.|
||Instance UUID that identifies the process in the system.|
||UUID of the job.|
||FQN of the job.|
||Specify a custom envirnment variable.|
Refer to the app selection and migration topic for examples of job environment variables.
In addition to job variables, the system will also expose and populate package variables, an example of which is shown below:
Service bindings are stored as environment variables:
<service-type>_URI <binding-name>_URI <service-name>_URI
There are specific binding varables for JDBC:
JDBC_<service-type>_URI <binding-name>_URI <service-name>_URI
JDBC_MYSQL_URI MYSQLSERVICE_URI MYSQL_URI
Refer to the Service binding documentation for details.
Apcera saves APC settings in the file
.apc. It normally saves this file in your home directory, but you can specify a different location by setting the
APC_HOME environment variable. See Installing APC for more information.