The dodil CLI

dodil is Dodil’s unified command-line tool — one binary that wraps every product (Ignite, K3, Scriptum, VBase) as a subcommand, sharing a single login and config.

Install

macOS & Linux

curl -fsSL https://cli.dodil.io | bash

The installer detects your OS and architecture, downloads the matching binary to ~/.local/bin/dodil, and makes it executable. If ~/.local/bin isn’t on your PATH, add it to your shell profile:

export PATH="$HOME/.local/bin:$PATH"

Windows

There’s no install script for Windows yet — download the binary directly and put it on your PATH. In PowerShell:

irm https://cli.dodil.io/dodil-windows-amd64.exe -OutFile dodil.exe

Pick the build that matches your machine: dodil-windows-amd64.exe, dodil-windows-arm64.exe, or dodil-windows-386.exe.

Binaries for every platform are served from cli.dodil.io as dodil-<os>-<arch> — linux (amd64/arm64/386), darwin (amd64/arm64), and windows (amd64/arm64/386).

Verify

dodil --help

Using the CLI

Each product is a subcommand of dodil:

For example:

dodil ignite app list
dodil k3 bucket list

Authenticate

Log in once — it applies to every product:

dodil login <service_account_id> <service_account_secret>

After login, your token and org are read from config, so you usually don’t pass --token or --org per command.

Config

Configuration is shared at ~/.config/dodil/config.yaml. Each value resolves in this order:

1. CLI flags (--api-endpoint, --token, --org)
2. Environment variables — DODIL_TOKEN, DODIL_ORG, and a per-product endpoint variable (IGNITE_API_ENDPOINT, K3_API_ENDPOINT, …)
3. Config keys — the product’s own section (ignite.*, k3.*, …) with a global.* fallback
4. Built-in defaults

Each product’s CLI guide notes its own env prefix and config namespace.

Per-product CLI guides

Each product’s docs cover its own commands in depth:

• Ignite — CLI Basics 
• K3 — CLI Basics 
• Scriptum — docs 
• VBase — docs