CLI / oroc config

oroc config

Inspect configuration values.

Usage#

oroc config [options] [<key-or-path>]

Options#

Option Description
--config=<path> use an explicit oro.toml/oro.ini file
--list list known configuration keys with current and default values
--key=<name> print the current value for a specific key
--describe=<name> print help and metadata for a specific key
-f, --format=<format> print the full configuration as 'toml', 'ini', or 'json'
--json shorthand for '--format=json'
--strict treat unknown or unset keys as errors (non-zero exit)
--log-file=<path> mirror logs to a JSON file
-h, --help show help

Notes#

Keys may be provided in flattened form (e.g., "filesystem_sandbox_enabled") or as TOML-style paths (e.g., "filesystem.sandbox_enabled").

A bare argument after 'config' is treated as a key query (for example, 'oroc config filesystem.sandbox_enabled').

Unknown keys are printed when present in the active configuration but are marked as undocumented. --format prints the merged effective configuration after applying oro.toml, local .ororc overrides, and CLI-selected config sources.

Use '--log-file=<path>' instead of the global 'oroc --json ...' flag when you need structured config output on stdout and logs at the same time.

Examples#

oroc config --list

list all known configuration keys with effective values

oroc config meta.version

print the effective value of meta.version

oroc config --describe webview.root

print the description, default, and source for webview.root

oroc config "ios.*"

glob-match a group of related keys

oroc config --format json

print the merged effective configuration as JSON

Source repository · Edit this page · View Markdown

Quick links

Type to search across the site. Use the up and down arrow keys to choose a result, Enter to open it, and Escape to close.