Synopsis
config command operates on the global configuration file at ~/.config/dorgu/config.yaml. Use dorgu init to create or re-initialize configuration files.
Subcommands
Configuration keys
Config merge order
Config merge order (highest priority first):
CLI flags > App
.dorgu.yaml > Workspace .dorgu.yaml > Global ~/.config/dorgu/config.yaml > Environment variables > Built-in defaultsconfig list and config get reflect the global config file. App-level overrides (from .dorgu.yaml) and CLI flags take effect at runtime but are not displayed by these subcommands.
LLM API key resolution
The LLM API key is resolved in the following order:- Environment variable —
DORGU_LLM_API_KEY(or provider-specific variables likeOPENAI_API_KEY) - Global config —
llm.api_keyin~/.config/dorgu/config.yaml - Interactive prompt — If neither is set, dorgu prompts you at runtime
Storing your API key in an environment variable is recommended over saving it in the config file, especially in shared or CI environments.
Examples
config list
Display all configuration keys with their current values:config get
Retrieve a single value by key:config set
Set a configuration value:config path
Show the resolved path to the configuration file:config reset
Reset all values in the global config file to built-in defaults:Related
- dorgu init — Create initial configuration files (app-level or global)
- dorgu generate — Generate Kubernetes manifests using the configured settings
- Command Overview — All CLI commands at a glance