Advanced installation options

When installing Axolet, you can set a number of advanced options if needed for your environment. Setting the advanced options in the Axoflow Console automatically updates the one-liner command that you can copy and run.

Advanced deployment options

Alternatively, before running the one-liner you can use one of the following methods:

Set the related environment variable for the option. For example:
```
export AXOLET_USER=syslogng
export AXOLET_GROUP=syslogng
```

Set the related URL parameter for the option. For example:

curl -fLsH 'X-AXO-TOKEN:random-generated' 'https://<your-tenant-id>.cloud.axoflow.io/setup.sh?type=AXOEDGE&platform=LINUX&user=syslogng&group=syslogng' | sh

Proxy settings

Use the http_proxy=, https_proxy=, no_proxy= parameters to configure HTTP proxy settings for the installer. To configure the Axolet service to use the proxy settings, enable the AXOLET_AVOID_PROXY parameter as well. Lowercase variable names are preferred because they work universally.

Installation options

You can pass the following parameters to the installation script as environment variables, or as URL parameters.

Note Running the provisioning command with sudo would mask environment variables of the calling shell. Either start the whole procedure from a root shell, or let the install script call sudo when it needs to. In other words: don’t add the sudo command to the provisioning command.

AXOLET_AVOID_PROXY


Default value:	`AXOLET_AVOID_PROXY=false`
Available values:	`true`, `false`

Description: If set to true, the value of the *_proxy variables will only be used for downloading the installer, but not for the axolet service itself. If set to false, the Axolet service will use the variables from the installer.

AXOLET_CAPS


Default value:	`AXOLET_CAPS=CAP_SYS_PTRACE`
Available values:	Whitespace-separated list of capability names with `CAP_` prefix.

Description: Ambient Linux capabilities the axolet service will use.

AXOLET_CONFIG_OVERWRITE


Default value:	`AXOLET_CONFIG_OVERWRITE=false`
Available values:	`true`, `false`

Description: If set to true, the configuration process will overwrite existing configuration (/etc/axolet/config.json). This means that the agent will get a new GUID and it will require approval on the Axoflow Console.

AXOLET_GROUP


Default value:	`AXOLET_GROUP=root`
Available values:	Any group name available on the host.

Description: Name of the group and Axolet will be running as. It should be either root or the group syslog-ng is running as.

AXOLET_INSTALL_PACKAGE


Default value:	`AXOLET_INSTALL_PACKAGE=auto`
Available values:	`auto`, `rpm`, `deb`, `tar`, `none`

Description: The method to use for installing the axolet binaries, the configure-axolet script, and the systemd service file. The configure-axolet script expects a pre-installed package when none is selected, and it will try to find the proper method for the current OS when it’s auto.

AXOLET_START


Default value:	`AXOLET_START=true`
Available values:	`true`, `false`

Description: Start axolet agent at the end of installation. Use false for preparing golden images. In this case axolet will generate a new GUID on the first boot after cloning the image.

If you are preparing a host for cloning with Axolet already installed, set the following environment variable in your (root) shell session, before running the one-liner command. For example:

export START_AXOLET=false
curl ... # Run the command copied from the Provisioning page

This way Axolet will only start and initialize after the first reboot.

AXOLET_USER


Default value:	`AXOLET_USER=root`
Available values:	Any username available on the host.

Description: Name of the user Axolet will be running as. It should be either root or the user syslog-ng is running as. See also Run axolet as non-root.