coulomb/repo-scoping
2
0
Fork 0
generated from coulomb/repo-seed
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Finalize repo-scoping runtime rename

Browse Source
This commit is contained in:
Bernd Worsch
2026-05-15 21:16:34 +02:00
parent 084159e51c
commit 28fad1b248
62 changed files with 445 additions and 305 deletions
Download Patch File Download Diff File Expand all files Collapse all files

30
docs/operations.md
View File

@@ -5,18 +5,18 @@ Repository Scoping service.
## Configuration
Configuration is read from environment variables with the `REPO_REGISTRY_`
prefix. That prefix is retained as an implementation compatibility detail after
the product rename from Repository Ability Registry to Repository Scoping.
Configuration is read from environment variables with the `REPO_SCOPING_`
prefix. The same naming is used by the import package and default local
database path so service identity stays aligned with Repository Scoping.
| Variable | Default | Purpose |
| --- | --- | --- |
| `REPO_REGISTRY_DATABASE_PATH` | `var/repo-registry.sqlite3` | SQLite database file used by the default store. |
| `REPO_REGISTRY_CHECKOUT_ROOT` | `var/checkouts` | Local checkout cache used during repository ingestion. |
| `REPO_REGISTRY_LLM_PROVIDER` | unset | Optional LLM provider name for candidate extraction. |
| `REPO_REGISTRY_LLM_MODEL` | unset | Optional model name passed to the configured LLM provider. |
| `REPO_REGISTRY_EMBEDDING_PROVIDER` | unset | Set to `hashing` to enable deterministic local hybrid search scoring. |
| `REPO_REGISTRY_LOG_LEVEL` | `INFO` | Log level for the `repo_registry.operations` structured event logger. |
| `REPO_SCOPING_DATABASE_PATH` | `var/repo-scoping.sqlite3` | SQLite database file used by the default store. |
| `REPO_SCOPING_CHECKOUT_ROOT` | `var/checkouts` | Local checkout cache used during repository ingestion. |
| `REPO_SCOPING_LLM_PROVIDER` | unset | Optional LLM provider name for candidate extraction. |
| `REPO_SCOPING_LLM_MODEL` | unset | Optional model name passed to the configured LLM provider. |
| `REPO_SCOPING_EMBEDDING_PROVIDER` | unset | Set to `hashing` to enable deterministic local hybrid search scoring. |
| `REPO_SCOPING_LOG_LEVEL` | `INFO` | Log level for the `repo_scoping.operations` structured event logger. |
## Health Checks
@@ -27,7 +27,7 @@ be checked locally:
{
"status": "ok",
"database": {
"path": "var/repo-registry.sqlite3",
"path": "var/repo-scoping.sqlite3",
"reachable": true,
"error": null
},
@@ -44,13 +44,13 @@ ingestion path.
## Structured Logs
Operational events are emitted through the `repo_registry.operations` logger as
Operational events are emitted through the `repo_scoping.operations` logger as
single-line JSON messages. Current events include repository registration,
analysis start/completion/failure, LLM extraction usage/failure, and review
decisions.
Configure the Python or ASGI server logging stack to route this logger to the
same sink as application logs. `REPO_REGISTRY_LOG_LEVEL` controls the logger
same sink as application logs. `REPO_SCOPING_LOG_LEVEL` controls the logger
level used by API-created service instances.
## SQLite Backup And Restore
@@ -60,18 +60,18 @@ continue while the backup is created:
```bash
mkdir -p backups
sqlite3 var/repo-registry.sqlite3 ".backup 'backups/repo-registry-$(date +%F).sqlite3'"
sqlite3 var/repo-scoping.sqlite3 ".backup 'backups/repo-scoping-$(date +%F).sqlite3'"
```
For the most conservative backup window, stop writes first, run the backup, then
resume the service. Verify a backup with:
```bash
sqlite3 backups/repo-registry-YYYY-MM-DD.sqlite3 "PRAGMA integrity_check;"
sqlite3 backups/repo-scoping-YYYY-MM-DD.sqlite3 "PRAGMA integrity_check;"
```
To restore, stop the service, move the current database aside, copy the backup to
`REPO_REGISTRY_DATABASE_PATH`, start the service, and verify `GET /health`.
`REPO_SCOPING_DATABASE_PATH`, start the service, and verify `GET /health`.
## PostgreSQL Migration Notes