Corredor Server
Environmental variables used by Corredor and API Server when connected to and communicating with Corredor.
Type | Default value | Description |
---|---|---|
|
||
|
|
This setting is used by both, Corredor and API Server. For Corredor server: where is server listening on For API server: where can Corredor server be accessed. Used by Corredor and API server. |
|
||
|
|
This is a setting for API server, will Corredor be used for server automation? Used by Corredor and API server. |
|
||
|
|
Connection timeout (from API server to Corredor) Used by API server. |
|
||
|
Location of the compose API (example: Used by API server. |
|
|
||
|
Location of the messagign API (example: Used by API server. |
|
|
||
|
Location of the system API (example: Used by API server. |
|
|
||
|
|
This setting is used by both, Corredor and API Server. For Corredor service: where is service listening on (gRPC) For API server: where can Corredor service be accessed. Used by Corredor and API server. |
|
||
|
|
If set to true, API server will log communication with Corredor and Corredor will log incoming requests. Used by Corredor and API server. |
|
||
|
|
Defaults to Used by Corredor and API server. |
|
||
|
|
Are events logged in one-line JSON or formatted to ease development? Used by Corredor. |
|
||
|
|
Corredor will log even more information Used by Corredor. |