Application Variables

GATEWAY_APPLICATION_MODE

Related information is available here → Modes of Operations

File

Section: application
Key: application_mode

Default

local All in one server that runs without server and client.

Possible Values

["local", "client", "server"]

GATEWAY_APPLICATION_AUTO_ACCEPT_EULA

To use gateway you must accept the EULA that can be found at: https://gateway.dev/licenses/eula. If you want to accept this without having to interact with acceptance on command line, this can be set to true. This config is useful in situations where running in a non-interactive mode such as server deployments.

Environment Variable

GATEWAY_APPLICATION_AUTO_ACCEPT_EULA

File

Section: application
Key: auto_accept_eula

Default

false

GATEWAY_APPLICATION_CLUSTER_ID

The ID that uniquely identifies a gateway instance or a cluster of related gateway instances if the gateway deployment utilizes core/runner nodes. This is also used to link a gateway core node to a commander instance so that automations can be sent to a particular cluster

Environment Variable

GATEWAY_APPLICATION_CLUSTER_ID

File

Section: application
Key: cluster_id

Default

cluster_1

GATEWAY_APPLICATION_WORKING_DIR

The location where gateway will store various files to work from.
Examples include the gateway database when GATEWAY_STORE_BACKEND=local, the gateway.log file when gateway is being run as a client, and the ssh known_hosts file.

Environment Variable

GATEWAY_APPLICATION_WORKING_DIR

File

Section: application
Key: working_dir

Default

Home directory of user running gateway
~/.gateway.d

References

For related information see → Using Config Variables.

For a list of command references see → Command References Index