Configuration & Environment

Weavori is designed to be zero-config: it works with defaults out of the box. When you do need to configure it, every option fits into one simple rule:

Flags override environment variables, which override config files.

This guide is the single source of truth for how Weavori is configured.

Configuration files

User config: ~/.weavori/config.yaml

Weavori stores user-specific state in a single YAML file, created automatically on first use:

The file holds only machine-specific state, never product constants:

• Saved database connection — written by weavori connect
• Cached subscription token — written by weavori login or an API key exchange
• Device identity — a random identifier generated on first run, used for anonymous usage tracking and the anonymous daily budget

You normally never edit this file — the CLI manages it. Deleting it is safe but resets everything: you'll need to run weavori connect again, weavori login again, and the anonymous daily budget restarts.

Project config: weavori.yaml

For per-project generation settings, Weavori reads a weavori.yaml file discovered by searching upward from your current working directory — so it works from any subdirectory and can be committed to your repository:

version: 1
generate:
  datasets:
    customers: ./data/customers.csv
  tables:
    orders:
      columns:
        total:
          formula: 'round(quantity * unit_price, 2)'
        customer_id:
          dataset: customers

Supported settings:

• generate.datasets — register CSV datasets by name (name: path/to/file.csv)
• generate.tables.<table>.columns.<column>.formula — computed column expression
• generate.tables.<table>.columns.<column>.dataset — dataset to sample values from
• generate.tables.<table>.columns.<column>.column — optional CSV column name (auto-detected when the dataset has a single column)

Project config is best-effort and merge-only: it fills gaps, never overrides explicit flags, and an invalid weavori.yaml logs a warning and is ignored rather than failing the run.

Session credentials: ~/.weavori/auth.yaml

OAuth session tokens from weavori login are stored in your operating system's keyring when available, with ~/.weavori/auth.yaml as the file fallback. weavori logout clears them.

Schema cache: ~/.weavori/cache/

Introspected schemas are cached here. See Schema & Caching Management for details.

Environment variables

Environment variables are the recommended way to configure CI and headless environments — see CI/CD Integration.

Precedence rules

Database DSN

If none is set, Weavori fails with a message showing the available options.

API key

An explicit API key always wins over any ambient session state — it is the reliable way to pin a CI run to a specific identity.

Output format

Authentication identity

See the authentication overview for the full flow.

Best practices by environment

Where things live