Docs / Operations Operate
Production Setup
A checklist for running EKOS beyond a laptop.
- [ ] One writer. One indexing job per workspace, or one console per home — never two consoles over one home, never more than one replica.
- [ ] Console in production mode (
EKOS_CONSOLE_PRODUCTION=true): OIDC, at least one owner, a session secret. Roles granted explicitly; API tokens for agents, never a person's sign-in. - [ ] TLS in front of the console or any
--tcp/--httpMCP server; MCP servers outside the console use--token-file. - [ ] Dedicated sources. Do not observe directories holding other projects' virtualenvs, build outputs or data dumps.
- [ ] Exclusions reviewed —
ekos config preview-scanbefore the first build;ignore-patternstakes exact directory or file names, not globs. Data dumps (oneINSERTper row) make commits slow. - [ ] Secrets — provider keys and database passwords from the environment, a keychain or the cloud's secret store, never in
ekos.toml(it holds only variable names). Add[security]patterns for your own secret shapes. - [ ] Live databases — a read-only user;
ekos database testconfirms writes are refused. - [ ] LLM spend — leave
[llm-description],[document-semantics]and[semantics] llm-definitionsoff in automation unless intended; in the console, Allow metered model calls per tenant;[llm] budget-usdrefuses a call that could exceed a budget;ekos llm usageshows what was spent. - [ ] Health checks —
/api/healthfor the console,ekos doctor --jsonper project. - [ ] Backups —
ekos home backup, scheduled, copied off the machine (--toobject storage). See Backup & Recovery. - [ ] Pin the version and read Upgrades before changing it.