config path

Print the file paths the CLI is reading config from. Use this when something looks wrong in config show and you want to know which file is supplying which profile.

apyx config path

• Synopsis
• Examples
  • Both files present
  • Project only
  • $XDG_CONFIG_HOME set
  • No config found
• Resolution rules
• Exit codes
• Related

Synopsis

apyx config path

No flags. Prints one line per source file the CLI loaded, in order: home first, project second. A profile defined in both files is ultimately governed by the project file’s version.

Examples

Both files present

$ apyx config path
/Users/jane/.apyx/config.json (home)
/Users/jane/work/apyx-sdk/apyx.config.json (project)

Project only

$ apyx config path
/Users/jane/work/apyx-sdk/apyx.config.json (project)

$XDG_CONFIG_HOME set

$ XDG_CONFIG_HOME=/Users/jane/Library/Preferences apyx config path
/Users/jane/Library/Preferences/apyx/config.json (home)
/Users/jane/work/apyx-sdk/apyx.config.json (project)

No config found

$ cd /tmp && apyx config path
No config found. Run `apyx config init`.

echo $?    # 1

Resolution rules

See Configuration → Resolution rules. The summary:

• ./apyx.config.json is the project config.
• ~/.apyx/config.json (or $XDG_CONFIG_HOME/apyx/config.json) is the home config.
• Project profiles fully replace home profiles of the same name — there’s no deep merge.

Exit codes

Related

• Configuration — schema and resolution rules.
• config show — print the merged contents.
• config init — create a project config.