Configuration
Veln reads configuration from a predictable stack: CLI flags win over environment variables, which win over a user config file, which wins over defaults. Exact keys vary by release — use veln help and veln config subcommands where available.
Environment variables
Common examples include API URL, device access token (minted by veln activate), machine identity, and gate-related settings. Do not commit secrets to git; use your shell, CI secrets, or a secrets manager.
Config file
Persistent options can live in a Veln config file under the user profile (path depends on OS). Use veln config validate or your build’s documented commands to check syntax before relying on it in automation.
Safe mode
Sensitive operations may require explicit flags or environment to avoid accidental unsafe runs in CI or shared machines — follow prompts and help text when the CLI refuses to proceed.