Commands
Syntax, options and behavior for every Rippler CLI command.
rippler sync
Sets up monitoring for your whole crontab in one go.
rippler sync [--dry-run] [--yes] [--project <shortID>] [--adopt-system]It creates a monitor for every job that does not have one and rewrites those
lines to run under exec. Start with --dry-run to see the plan:
$ rippler sync --dry-run
your crontab
create 0 3 * * * backup.sh
create @daily cleanup.sh
keep */5 * * * * already monitored
skip @reboot no schedule to expect pings against
/etc/cron.d/backup (system file — sync will not edit it)
~ 0 3 * * * backup.sh
Re-run with --adopt-system to create monitors for the 1 job(s) above and
print the lines to paste in.| Flag | What it does |
|---|---|
--dry-run | Print the plan and stop. Nothing is created or changed. |
--yes | Skip the confirmation prompt. For scripts. |
--project | Put new monitors in this project instead of the first one. |
--adopt-system | Also create monitors for jobs in /etc/crontab and /etc/cron.d/, printing the lines to paste in. |
Jobs outside your own crontab are always reported; they are never edited. See Where it looks.
Your crontab is backed up before anything is changed. See crontab handling for what it will and will not touch.
If the crontab needs more monitors than your plan has room for, sync says so
before it creates anything:
! this needs 12 monitor(s) and your plan has room for 4.You can still run it. It creates what fits, wraps only those lines, and leaves the rest of the crontab untouched so a later run can pick them up.
rippler upgrade
Replaces this executable with the published one.
rippler upgrade [--check]See Upgrading for what it checks and where it writes.
rippler exec
Runs one command and reports it. This is what sync puts in your crontab, and
you can use it directly:
rippler exec 7gM7Qy7 -- /usr/local/bin/backup.sh --fullIt tells Rippler the run has started, then reports success or failure based on the command's exit code, along with how long it took.
It does not change how the job behaves:
- Your command's exit code is passed through, so cron behaves as it did before.
- stdout and stderr are passed through, so you still get your cron mail and your logs.
- If Rippler is unreachable, your job still runs. Failed pings are dropped, not turned into errors.
rippler list
Shows every monitor in your team.
Nightly backup 7gM7Qy7 Up At 03:00 AM
poll.sh jGDc_zz Down Every 15 minutesrippler projects
Lists your projects and their short ids, for sync --project.
rippler login
rippler login [--token <token>] [--url <api-url>]Saves your API token after checking it works. See Install.
rippler version
Prints the version you have installed.
Building from source
You do not need this to use the CLI. The installer gives you a prebuilt binary. To build it yourself:
pnpm build:cliBuilding for other platforms needs a released Bun, not a canary. bun build --compile downloads
a published runtime for each target and canaries are only published for the machine you are on.
Run bun upgrade --stable if the build tells you so.