Operations
Maintenance notes for running OrcAI.
This page collects operational notes that are clear from the repository. It is not a complete production runbook yet.
Draft runbook
This page intentionally favours known-safe checks over speculative production advice.
Migrations
Apply application database migrations with:
bun run --filter @orcai/db migrateGenerate a new Drizzle migration during development with:
bun run --filter @orcai/db generateApply the SpiceDB schema with:
bun run --filter @orcai/spice-db upInspect SpiceDB schema migration status with:
bun run --filter @orcai/spice-db statusWorkers
Keep workers running alongside the app. If workers are stopped, uploads and scheduled maintenance jobs may remain queued.
Asset Processing
If OCR or extraction fails, verify:
- Worker process is running.
- Tesseract is installed when running workers on the host.
KREUZBERG_OCR_LANGUAGEonly references installed language packs.- The AI endpoint supports the configured
GENERAL_MODEL. - Object storage credentials and bucket setup are valid.
Retrieval
If retrieval quality or indexing fails, verify:
OPENAI_COMPATIBLE_BASE_URLandOPENAI_COMPATIBLE_API_KEY.EMBEDDING_MODEL.EMBEDDING_DIMENSIONS.- Qdrant availability and API key.
Do not change embedding model or dimensions on a live indexed dataset without recreating the collection and reindexing.
SpiceDB Connectivity
If SpiceDB connections fail, verify:
SPICEDB_ENDPOINT.SPICEDB_TOKEN.SPICEDB_SECURITYmatches your deployment mode.
TODO
Add backup and restore guidance, health checks, alerting recommendations, log locations, common failure signatures, upgrade steps, and compatibility policy.