You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Related Pages:

Environment Variables

The E2E Bridge provides some environment variables that are strongly recommended to be used by developers in their code:

VariableDescriptionDefault
PORTNode.js service port-
CONFIG_DIRPath to the configuration directory of the service (within the working directory of the service).
  • All configuration files (e.g. service settings) that are stored in this location will survive a Node.js service update. Files that have been saved to the working directory only, will be deleted on update.
  • This directory will be created by the Bridge on service startup, if not existent.
repository/config/local
E2E_CONF_ROOTIf you use the e2e-conf Node.js module, you can initialize e2e-conf with E2E_CONF_ROOT. This is especially useful if your e2e-conf is not a top level dependency but a sub-module dependency.repository
E2E_LOGS

If the Node.js service writes log files in this directory, you can view them in the E2E Bridge.

  • If the log file keeps growing, you should rotate the log file per day and use this naming pattern:
    <prefix>_YYYY-MM-DD.log.
  • If the log file has a fixed size, you can use the naming pattern <prefix>.log.

Do not use the following prefixes: start, stdout, stderr and transaction. They are reserved prefixes by the E2E Bridge.

logs
These special environment variables are displayed on the details tab of any Node.js service. Add and configure them on tab Environment Variables of the Node.js service (see Setting Environment Variables for Node.js Services).

  • No labels