Setup

Get the binary

Either grab a pre-built binary for your OS/arch, or build it yourself from the cmt source directory (requires Go):

make build      # current platform only -> bin/cmt
make compile     # Linux, Windows, macOS -> bin/

Install

Copy the binary somewhere on PATH, and make it executable:

sudo cp bin/cmt /usr/local/bin/cmt
sudo chmod +x /usr/local/bin/cmt
cmt version

(On Windows, put cmt.exe wherever you’d place any other CLI tool and add it to PATH.)

Bootstrap a configuration

Everything cmt reads/writes lives under one cmt directory, ~/.cavaliba/cmt/ by default. Running cmt with no config file yet present creates a starter conf.yml there automatically, with sane local defaults (cpu/memory/disk/mount/load/ping checks, cli output):

cmt

Check what got created:

cmt checkconfig      # print the merged effective config and exit
cmt -l                # run once, long/detailed output

From here, see Configuration to point cmt at Cavaliba (global.url/client_id/client_secret) or add your own checks, and Options for how to actually schedule it (--cron via an external scheduler, or the built-in cmt daemon loop).

To use a different location instead of ~/.cavaliba/cmt/, pass --conf (a directory, or a specific config file whose parent directory becomes the cmt directory):

cmt --conf /etc/cmt/conf.yml