CLI Basics
Ignite runs as a plugin under the unified dodil CLI. Every command is invoked as:
dodil ignite <command> [subcommand] [flags]Install & authenticate
The dodil CLI bundles every product, Ignite included. Install it and run dodil login once — see Install the CLI for the full instructions (macOS, Linux, Windows), the shared config file, and the value-resolution order. After login, Ignite reads your token and org from config, so you don’t pass them per command.
Config
Ignite reads the shared dodil config (see Install the CLI ). Its product-specific bits: the endpoint environment variable is IGNITE_API_ENDPOINT, and config keys live under ignite.* (with a global.* fallback). Point the CLI at the gRPC endpoint — rpc.dev.dodil.io:443 (staging) or rpc.dodil.io:443 (production); TLS is on by default, and --debug disables it for local development. Override any value per command with --api-endpoint, --token, or --org.
Global Flags
| Flag | Description |
|---|---|
-o, --output | Output format: table (default), json, yaml, wide |
--api-endpoint | Override the gRPC endpoint |
--token | Override the bearer token |
--org | Override the organization |
--debug | Enable debug mode (disables TLS) |
--timeout | Request timeout (default 5m) |
Command Groups
Under dodil ignite:
app— Compute app lifecycledraftversionexecution(exec)invokemodels— managed inferencesecret— credential slotsbuild— remote image buildsconfig
Exit Codes
The CLI maps gRPC status codes to process exit codes:
| Exit code | gRPC status |
|---|---|
| 2 | InvalidArgument |
| 3 | Unauthenticated |
| 4 | PermissionDenied |
| 5 | NotFound |
| 6 | AlreadyExists |
| 7 | ResourceExhausted |
| 8 | DeadlineExceeded |
| 9 | Unavailable |
| 10 | Internal |
See also
- Install the CLI — the
dodilCLI across all products - Conventions — transport, auth, wire format
- Compute — the app surface the
dodil ignite appcommands target - Auth and Access