Repo docs

Per-repo documentation — each repo's docs/ and README, ingested and associated with the repo. Rendered through the <<<RepoDocs>>> tag.

← gitlab__testmonkeyalpha-group__jazz-forge__jazz_config docs · README.md

jazz-config

Descriptive install + config for jazz from a single TOML spec (jazz.toml) — data, not a DSL. One source of truth describes the modules to install and how each service is configured; this tool renders the derived artifacts so config stops being scattered across Dockerfiles/env/compose.

Use

python -m jazz_config plan     --spec jazz.toml      # human-readable plan of all parts
python -m jazz_config env      --spec jazz.toml > .env
python -m jazz_config compose  --spec jazz.toml > docker-compose.generated.yml
python -m jazz_config check    --spec jazz.toml      # health-check live services

The spec (jazz.toml)

- [install] — modules (dep order), third_party, system_deps (consumed by jazz-provision.sh) - [config] — global env, rendered to .env - [services.X]compose/run/external, image/build, port, health, env, depends_on, volumes - [mcp.X] — stdio MCP servers (command, env)

compose-flagged services render into a docker-compose.yml (ports, volumes, environment, depends_on filtered to composed services, healthcheck from port+health). Adding a module + service becomes a single spec entry instead of editing compose + env + the provisioner.