apunkt/omnigraph
1
0
Fork 0
mirror of https://github.com/ModernRelay/omnigraph.git synced 2026-06-15 01:55:13 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions

docs: document global-first layered config, config view, and use

Browse source 
Add a Layered config section to cli-reference.md (precedence chain, OMNIGRAPH_HOME/
CONFIG/XDG resolution, ~/.omnigraph layout, merge semantics) and the config view /
use command rows; note global-first in cli.md; record the layered-config test surface
in testing.md; update the RFC-002 implementation-status banner (V1-remainder landed).
This commit is contained in:
Ragnor Comerford 2026-06-05 11:54:23 +02:00
parent d52cd1d0a3
commit 1a6371d015
No known key found for this signature in database
4 changed files with 58 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

10
docs/user/cli.md
View file

@ -149,6 +149,16 @@ The config file can also define:
When policy is enabled, `schema apply` is authorized through the
`schema_apply` action and is typically limited to admins on protected `main`.
### Global-first layering
The CLI merges a user-global `~/.omnigraph/config.yaml` under the project
`./omnigraph.yaml`, so it works from any directory with no project file. A graph,
server, or default defined only in the global config is fully usable. Inspect the
result with `omnigraph config view [--show-origin] [--resolved <graph>]`, and set the
active default graph with `omnigraph use <graph>`. Precedence, env vars, and merge
rules are in [cli-reference.md](cli-reference.md#layered-config-global-first). The
server is unaffected — it reads only its project/`--config` deployment manifest.
## Deprecated names
The CLI was renamed to align with the HTTP server's canonical endpoint