The production CLI and runtime are released as versioned Linux amd64 artifacts. The runtime archive follows the naming convention:
The installer stages the runtime matching the exact CLI version. After the CLI and release bundle are present, initialize the deployment:
init creates a durable deployment UUID, generates deployment-owned secrets, writes production configuration, and installs/verifies the staged runtime bundle.
A new initialization writes state under /var/lib/leamout and configuration under /etc/leamout. Re-running init preserves an existing valid deployment identity and secrets while re-verifying/installing the matching runtime bundle.
Then validate the local installation:
and start it:
The target design describes hosted activation and a public bootstrap endpoint, but the current leamout init implementation does not accept an activation token. Do not rely on --activation-token until that workflow ships.
