Corredor Server configuration
-
type:
string
-
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.
-
default:
corredor:80
-
type:
bool
-
description: This is a setting for API server, will Corredor be used for server automation?
-
default:
false
-
type:
duration
-
description: Connection timeout (from API server to Corredor).
-
default:
1m
-
type:
string
-
description: Location of the Corteza server API. {host} is replaced with value from env variables (in this order:
CORREDOR_EXEC_CSERVERS_API_HOST
,DOMAIN
,HOSTNAME
,HOST
), {service} is replaced dynamically inside Corredor withcompose
,system
ormessaging
. -
default:
https://api.{host}/{service}
-
type:
string
-
description: Hostname used for the template.
-
default: ``
-
type:
boolean
-
description: 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.
-
default:
corredor
-
type:
string
-
description: Defaults to
trace
whenCORREDOR_DEBUG
istrue
, defines amount of log information outputed. -
default:
info
-
type:
boolean
-
description: Are events logged in one-line JSON or formatted to ease development?
-
default:
false
-
type:
boolean
-
description: Corredor will log even more information.
-
default:
false
-
type:
boolean
-
description: Corredor will auto update script dependencies found in
package.json
files. -
default:
true
-
type:
boolean
-
description: Server scripts are enabled.
-
default:
true
-
type:
boolean
-
description: Corredor will reload server-scripts on change.
-
default:
true
-
type:
boolean
-
description: Client scripts are enabled.
-
default:
true
-
type:
boolean
-
description: Corredor will reload client-scripts on change.
-
default:
true