Get started
Installation
Download, extract, authorize, and verify clmbot v0.6.6 packages on macOS, Linux, and Windows.
This page explains how to install clmbot v0.6.6 on the five supported platform builds.
Choose a platform
| Operating system | Architecture | Package format |
|---|---|---|
| macOS | amd64 | tar.gz |
| macOS | arm64 | tar.gz |
| Linux | amd64 | tar.gz |
| Linux | arm64 | tar.gz |
| Windows | amd64 | zip |
All packages are available from the download page without registration or login. The sslTrus CDN is currently the only official file source.
Verify SHA256
Verify file integrity before running any binary. The download page publishes the official SHA256 value and platform-specific verification guidance. If the checksum differs, do not run the file; download it again or report the problem on GitHub.
Install on Linux or macOS
-
Upload the package to the target server and extract it. This example uses Linux amd64; use the actual release filename:
tar -xzf clmbot-v0.6.6-linux-amd64.tar.gz -
Add execute permission to the binary:
chmod 755 clm-bot-linux-amd64 -
Confirm that it runs and inspect available subcommands:
./clm-bot-linux-amd64 --help
The archive name and extracted binary name may differ.
clm-bot-linux-amd64is an example; replace it with the filename you actually extract.
Install on Windows
-
Download the Windows amd64 zip package.
-
Extract it to a stable directory, such as
C:\clmbot\, because scheduled tasks will refer to that path. -
Open PowerShell or Command Prompt in that directory and run
--helpwith the actual extracted executable name:.\clm-bot-windows-amd64.exe --help
Windows does not require chmod. If Windows reports that the file is blocked, inspect the Unblock option in file properties and evaluate it under your organization’s security baseline.
Run with least privilege
Do not run clmbot permanently as root or Administrator. After installation, create a dedicated system account and grant only the certificate-directory and service-reload permissions it requires. See Least privilege.
Next steps
- Getting started: complete a minimum viable deployment in ten steps
- Configuration: initialize an upstream connection
- Deployment targets: review the supported target catalog
