Skip to content

Single Line

A simple installation script for most Linux targets, installs the most recent version of the 10x Engine.

The script downloads the Runtime native binary and config files from the latest release, installs the engine and sets up the necessary environment variables.

Quick installation
curl https://raw.githubusercontent.com/log-10x/pipeline-releases/main/install.sh | bash

Flavors this script installs

All three flavors have a Linux artifact, so on Linux (amd64 and arm64, glibc) the script installs any of them:

Flavor Artifact Linux macOS
Runtime (default) native binary --flavor runtime --flavor runtime, or Homebrew
Runtime (JVM) .deb / .rpm --flavor runtime-jvm .dmg on the releases page
Compiler .deb / .rpm --flavor compiler brew install --cask log-10x/tap/log10x-cloud

The macOS artifacts for the Compiler and for Runtime (JVM) are .dmg packages, which this script does not mount. Windows is covered by the PowerShell installer.

Configuration options

The script accepts the following parameters:

  • --flavor <runtime|runtime-jvm|compiler>: install a target flavor (Runtime, the default, Runtime (JVM), or Compiler).
  • --version <VERSION>: install a specific version instead of latest.
  • --no-env-setup: only install binaries without setting environment variables.
  • --no-config: only install binaries without config modules (Advanced users).
  • --no-symbols: only install binaries without pre-compiled 10x symbols (Advanced users).
Example - install version 1.0.0, compiler flavor, and no configuration files
curl https://raw.githubusercontent.com/log-10x/pipeline-releases/main/install.sh | bash -s -- --version 1.0.0 --flavor compiler --no-config

Environment Variables

In order to set up 10x environment variables globally, the install script will invoke sudo

If you want to set up the environment variables manually, pass the --no-env-setup param to the install script (see above)

The following environment variables are recommended:

Variable Description Purpose Sample value
TENX_HOME 10x installation folder /opt/tenx-edge
TENX_MODULES path to 10x modules automatic modules detection instead of manually specifying includepaths $TENX_HOME/lib/app/modules
TENX_CONFIG path to 10x configuration automatic configuration detection instead of manually specifying includepaths /etc/tenx/config
TENX_SYMBOLS_PATH path to pre-compiled symbols automatic symbols detection instead of manually specifying symbolPaths /etc/tenx/symbols
TENX_BIN 10x executable allows 10x Engines and custom integrations to invoke additional engines if needed $TENX_HOME/bin/tenx

Additionally, it's recommended to add $TENX_HOME/bin to your PATH, so you can invoke tenx from everywhere

For details on how the engine locates modules and configuration files, see Paths.