primatekuntech/triton-install
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs: expand host-bound licence instructions with machine ID details

Browse source 
Clarifies the exact installer output format, emphasises that the Machine ID
is stable (SHA-3-256 of /etc/machine-id, set once at OS install), and shows
how to retrieve it at any time by re-running the install command.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
Amir Yahaya 2026-05-20 07:34:03 +02:00
parent bad2a6f130
commit fb80b3e21f
1 changed files with 21 additions and 8 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

27
README.md
View file

@ -71,22 +71,35 @@ Also delete all data (irreversible):
curl -fsSL https://raw.githubusercontent.com/primatekuntech/triton-install/main/get.sh | sudo bash -s -- --uninstall --purge-data curl -fsSL https://raw.githubusercontent.com/primatekuntech/triton-install/main/get.sh | sudo bash -s -- --uninstall --purge-data
``` ```
## Host-bound licences (optional) ## Host-bound licences
Your vendor can issue an offline `.lic` file that is cryptographically bound to a specific host Your vendor can issue an offline `.lic` file that is cryptographically bound to a specific host
so it cannot be installed on any other machine. so it cannot be used on any other machine.
**To get a host-bound licence:** **To get a host-bound licence:**
1. Run `install.sh` on the target server — the output prints a **Machine ID** line: 1. Run the installer on the target server. At the end of the output you will see:
``` ```
[manage-server] ── Host Machine ID ──────────────────────────────────────────────────────
[manage-server] Provide this value to your vendor when requesting a host-bound .lic file.
[manage-server] Machine ID (SHA-3-256): <64-hex-chars> [manage-server] Machine ID (SHA-3-256): <64-hex-chars>
[manage-server] ────────────────────────────────────────────────────────────────────────
``` ```
2. Share that value with your vendor when requesting the `.lic` file. 2. Share the 64-character hex value with your vendor.
3. The vendor enters it in the License Portal when generating the offline token. 3. The vendor enters it in the License Portal when generating the offline `.lic` token.
4. Install as usual — the Manage Server verifies the binding at every startup. 4. Re-run the installer with the new `.lic` file — the Manage Server verifies the binding at every startup.
For air-gapped deployments without host binding the `.lic` file is portable but anyone who **The Machine ID is stable.** It is a SHA-3-256 hash of `/etc/machine-id`, which is written once
at OS installation and never changes. Container restarts, image upgrades, and re-running the
installer will always produce the same value.
To retrieve the Machine ID at any time without re-installing, simply re-run the install command:
```bash
curl -fsSL https://raw.githubusercontent.com/primatekuntech/triton-install/main/get.sh | sudo bash -s -- --license-file /path/to/license.lic
```
For air-gapped deployments without host binding the `.lic` file is portable, but anyone who
obtains the file can run a second instance. Host binding removes that risk. obtains the file can run a second instance. Host binding removes that risk.
## Requirements ## Requirements