cortexdb-grpc

Overview ¶

Command cortexdb-grpc serves the pkg/cortexdb facade over gRPC.

Configuration (flags override env; .env is loaded when present):

CORTEXDB_PATH        SQLite file path (default ~/.cortexdb/cortexdb.db)
CORTEXDB_GRPC_ADDR   listen address (default 127.0.0.1:47821)
CORTEXDB_GRPC_TOKEN  bearer token; empty disables auth
OPENAI_BASE_URL      OpenAI-compatible base URL enabling embeddings
OPENAI_API_KEY       API key for the embeddings endpoint
CORTEXDB_EMBED_MODEL embedding model name (default text-embedding-3-small)
CORTEXDB_EMBED_DIM   embedding dimension (default 1536)
CORTEXDB_KEY_FILE    JSON file of scoped API keys (replaces the single token)
CORTEXDB_BACKUP_DIR  where AdminService.Backup may write
CORTEXDB_HTTP_ADDR   also serve REST + /metrics + /debug/vars here

`cortexdb-grpc -health` probes a server already running at -addr instead of starting one, so the same binary is its own liveness check. See deploy/ for systemd units and container images that use it.

`cortexdb-grpc -version` prints the version of the binary itself and exits, touching no database, no .env and no network. -health reports the version of a server that is already running; this reports the version of the file on disk, which is the question you have after copying a new binary into place and before restarting anything. Without it the only way to tell two builds apart was to compare their checksums against a build you still had.