a04a16c717
HAIKU_RAG_DB and DB_PATH are gone: a capability covers what the configuration places or the db_path it is given, and the app backend and the AG-UI example load their configuration as the CLI does. The compose files point HAIKU_RAG_CONFIG_PATH at the mounted haiku.rag.yaml, which places the database at /data where DB_VOLUME is mounted; the backend refuses a configured set since it serves one database. The chat scopes a selection by source only over a set and names databases on filter rows only across several. Docstrings, docs and test fixtures stop describing an unnamed database; every database a search, listing or citation reports carries a name. |
||
|---|---|---|
| .. | ||
| capabilities | ||
| configuration | ||
| img | ||
| stylesheets | ||
| apps.md | ||
| benchmarks.md | ||
| changelog.md | ||
| chat.md | ||
| cli.md | ||
| custom-pipelines.md | ||
| development.md | ||
| index.md | ||
| ingester.md | ||
| installation.md | ||
| mcp.md | ||
| overview.md | ||
| python.md | ||
| remote-processing.md | ||
| tools.md | ||
| tuning.md | ||
| tutorial.md | ||