Install Aurum

Aurum ships as a self-authenticating installer. A single command downloads and verifies the release, then installs the CLI, daemon, SDK, and CMake package.

Installer

curl -fsSL https://www.autech.pro/downloads/aurum/stable/install.sh | bash

The installer is version-pinned at release time. Every copy embeds the release version, the artifact URL, and the SHA-256 digest of the archive it installs. The script refuses to install anything other than its authenticated artifact.

Tip

To verify without installing, pass --verify-only. Use -t TARBALL to install from a local copy of the authenticated release archive.

Release contract

Release packages are built for Linux on x86_64. Each install delivers:

  • the aurum CLI;

  • the aurumd runtime daemon;

  • C++23 SDK headers and libraries;

  • the Aurum CMake package;

  • released venue packages.

Running make install from a source checkout builds and installs a traceable development snapshot such as 0.1.0-dev.4aa6679. Release automation passes an explicit stable version instead. The selected version is embedded consistently in the CLI, daemon, archive metadata, and generated installer.

The installation is atomic: the release tree is staged under a temporary directory, validated, and moved into place in a single mv operation. A pre-install smoke test runs aurum version and aurumd --help before the tree is committed to the prefix.

Install prefix

The default prefix depends on the invoking user:

  • Non-root: ~/.local

  • Root: /usr/local

When a terminal is available, the installer asks for the prefix:

## Where should AURUM be installed ? [/home/user/.local]

Press Enter to accept the default. The installer confirms ~/ expansion and asks before creating a missing directory. Use --prefix DIR to choose a different location or --yes to skip prompts. If the prefix requires elevated privileges, the installer invokes sudo for the single commit transaction.

Shell configuration

After installation the installer can add the prefix’s bin directory and Aurum shell completion to ~/.bashrc or ~/.zshrc. The content is contained in a replaceable managed block:

# BEGIN AURUM CONFIG
# PATH and shell completion
# END AURUM CONFIG

An existing complete block is replaced in place. Ambiguous, duplicate, or incomplete markers are never modified automatically. Use --shell-config to enable this update explicitly and --no-shell-config to disable it; --yes alone does not edit shell startup files. The uninstaller removes a valid managed block while preserving all configuration outside it.

During uninstallation, active daemon processes and installed user units are handled first. The uninstaller then asks whether to remove ${AURUM_HOME:-~/.aurum}; the default answer preserves user data. Once these decisions are complete, the installed program is removed without another confirmation prompt. In a non-interactive session user data is preserved; passing --yes also confirms its removal.

Verify the installation

After installation, confirm the toolchain is reachable:

aurum version
aurum info

If the shell cannot find aurum, add the install prefix’s bin directory to PATH and open a new shell.

Strategy toolchain

Strategy projects compile as C++23. Use the compiler and CMake toolchain approved for your Aurum release. aurum compile and aurum run invoke that toolchain for the project; users do not build the Aurum product itself.

Managed environments

A managed Forge workspace or authorized environment may already provide the compatible CLI, SDK, and toolchain. Verify it with aurum version and continue to Quickstart.

Next step

Create and run a project with Quickstart.