Install
One binary, no runtime required.
The CLI is compiled per platform and bundles everything it needs, so there is no Node, Bun or npm to install on the target machine.
Download
Grab the binary for your platform, make it executable, and put it on your PATH:
# macOS (Apple silicon)
curl -fsSL -o rippler https://github.com/ramonfritsch/rippler/releases/latest/download/rippler-darwin-arm64
chmod +x rippler
sudo mv rippler /usr/local/bin/| Platform | File |
|---|---|
| Linux, x86_64 | rippler-linux-x64 |
| Linux, ARM64 | rippler-linux-arm64 |
| macOS, Intel | rippler-darwin-x64 |
| macOS, Apple silicon | rippler-darwin-arm64 |
| Windows, x86_64 | rippler-windows-x64.exe |
Put it somewhere on the PATH that cron can see. Cron runs with a very small
PATH — usually /usr/bin:/bin — so /usr/local/bin is a safe choice, and
~/bin usually is not.
Log in
rippler loginIt asks for your API token, which is under Account → API in the app. The token is checked before it is saved, so a typo fails immediately rather than silently.
It is written to ~/.rippler/config.json with chmod 600. The token carries your
team membership, so treat it like a password — anyone holding it can read and
create monitors in your team.
Without logging in
Every command reads these, which is what CI and containers usually want:
| Variable | Purpose |
|---|---|
RIPPLER_API_TOKEN | Use this token instead of the stored one. |
RIPPLER_API_URL | Point at a different server. Defaults to https://api.rippler.io. |
RIPPLER_CONFIG | Where the config lives. Defaults to ~/.rippler/config.json. |
Building it yourself
pnpm build:cliCross-compiling needs a released Bun, not a canary — bun build --compile
downloads a published runtime for each target, and canaries are only published for
the host. Run bun upgrade --stable if the build tells you so.