Skip to content

Configuration

NEMAR CLI configuration and settings.

OSPath
macOS~/.config/nemar/config.json
Linux~/.config/nemar/config.json
Windows~/.config/nemar/config.json

The CLI standardizes on ~/.config/nemar/config.json for every platform. On first run it performs a one-time migration: if a legacy nemar-nodejs/config.json exists at the old OS-native location (~/Library/Preferences/nemar-nodejs/ on macOS, %APPDATA%\nemar-nodejs\ on Windows, or ~/.config/nemar-nodejs/ on Linux), it is copied to the standardized path. Set NEMAR_CONFIG_DIR to override the directory.

The config is multi-account: a top-level activeAccount names the account in use, and the accounts map holds the per-account settings keyed by NEMAR username.

{
"activeAccount": "johndoe",
"accounts": {
"johndoe": {
"apiKey": "nemar_...",
"apiUrl": "https://api.nemar.org",
"username": "johndoe",
"email": "[email protected]",
"githubUsername": "johndoe",
"sandboxCompleted": true,
"sandboxDatasetId": "nm099999",
"dismissedNoticeIds": []
}
}
}

Use nemar auth switch [username] to change the active account. The apiUrl field defaults to https://api.nemar.org; the CLI rewrites any stored URL pointing at a retired backend to this default on startup.

Environment variables override config file settings:

VariableDescription
NEMAR_API_KEYAPI key for authentication
NEMAR_API_URLAPI base URL (default: production)
  1. Command-line flags
  2. Environment variables
  3. Config file
  4. Defaults
Terminal window
nemar auth status
# Shows config path
Terminal window
nemar auth logout

You can edit the config file directly, but using CLI commands is recommended.