Install

macOS and Linux

curl -fsSL https://rippler.io/cli | sh

Windows

powershell -c "irm rippler.io/cli.ps1|iex"

Check it worked:

rippler version

The installer picks the right binary for your machine, verifies it against the published checksum, and puts it on your PATH. On macOS and Linux it goes to /usr/local/bin. On Windows it goes to %LOCALAPPDATA%\Rippler\bin. Open a new terminal afterwards so the PATH change takes effect.

The CLI is a single executable with everything bundled in, so the machine running your cron jobs needs no Node, no Bun and no npm.

Installing somewhere else? Set RIPPLER_INSTALL_DIR. Pick a directory on cron's PATH. Cron runs with a very small PATH, usually just /usr/bin:/bin, so ~/bin often does not work under cron even though it works in your shell.

Upgrading

rippler upgrade

It downloads the executable for your machine, checks it against the published SHA256SUMS, and moves it into place. rippler upgrade --check reports whether one is available without installing it.

The published filenames are stable, so upgrade compares the checksum of the executable you are running with the published one. If they match, nothing is done.

$ rippler upgrade
Checking https://static.rippler.io/cli/rippler-linux-x64
Downloading rippler-linux-x64
Upgraded. /usr/local/bin/rippler

The CLI usually lives in /usr/local/bin, which your user cannot write to. upgrade says so and tells you to re-run it with sudo.

A running rippler exec is not disturbed. The swap is a rename, so a job cron started mid-upgrade finishes on the executable it began with. Nothing upgrades on its own. It only happens when you run the command.

The checksum protects against a corrupted or truncated download. It is served over HTTPS from the same host as the executable, so it is not a signature. It is the same trust model as the install command above.

Log in

rippler login

It asks for your API token. Get it from Account → API in the app.

The token is checked before it is saved, so a typo fails immediately. It is written to ~/.rippler/config.json with permissions 600.

Treat the token like a password. Anyone who has it can read, create and delete monitors in your team. Rotate it from Account → API if it leaks.

Running without logging in

For CI, containers and anywhere you do not want to store a file, set these instead:

Variable	What it does
`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 file lives. Defaults to `~/.rippler/config.json`.

RIPPLER_API_TOKEN=rp_… rippler list

Installing by hand

To read the install script first, run curl -fsSL https://rippler.io/cli without the | sh. Or install by hand:

# Swap the filename for your platform from the table below
curl -fsSL -O https://static.rippler.io/cli/rippler-darwin-arm64
curl -fsSL -O https://static.rippler.io/cli/SHA256SUMS

# On Linux: sha256sum --ignore-missing -c SHA256SUMS
shasum -a 256 --ignore-missing -c SHA256SUMS

chmod +x rippler-darwin-arm64
sudo mv rippler-darwin-arm64 /usr/local/bin/rippler

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`

These URLs are stable and always point at the current release.

Rename the file after you check it. SHA256SUMS lists files by their published names, so if you download with curl -o rippler, shasum reports that nothing was verified.

Pinning a version

The URLs above always point at the current release, which suits a laptop but not a Dockerfile or a config-management run. Every release is also published at a path of its own, which never changes:

https://static.rippler.io/cli/v1.5.0/rippler-linux-x64
https://static.rippler.io/cli/v1.5.0/SHA256SUMS

The installer takes a version too:

RIPPLER_VERSION=1.5.0 curl -fsSL https://rippler.io/cli | sh

$env:RIPPLER_VERSION='1.5.0'; irm rippler.io/cli.ps1 | iex

Because a versioned file never changes, its checksum can be pinned beside it.

The current version number is published as plain text, so a script can read it without parsing anything:

curl -fsSL https://static.rippler.io/cli/LATEST

rippler upgrade always tracks the current release, whichever version you installed. Pinning changes what you install, not what upgrading gives you.

Monitor your crontab

Set up your crontab with rippler sync, or see every command.