Docs / Operations Operate
Deployment
EKOS is a single binary plus a directory; deploy it as a job that refreshes an index and a server that reads it.
There is no daemon and no external database to run. A deployment has two roles:
| Role | Command | Writes? |
|---|---|---|
| Indexer | ekos build … commit on a schedule or on change |
yes |
| Server | ekos mcp serve (stdio, --tcp, or --http) |
no (except the two review tools) |
Single host
# indexer (cron / CI)
ekos build && ekos recover && ekos resolve --force && ekos compile && ekos commit --yes
# server for URL-only clients, behind a TLS reverse proxy
ekos mcp serve --workspace /srv/ekos/workspace --http 127.0.0.1:8080 --token-file /etc/ekos/mcp.token
Containers
The repository contains a development Dockerfile.dev and docker-compose.dev.yml. There is no official production image yet; build the binary with cargo build --release in ekos/ and copy target/release/ekos into your own image with the workspace as a volume.
Larger scale
Partitioned storage (single machine) and distributed mode (coordinator + compile workers + query workers + gateway, optionally with S3-compatible object storage) are covered in Storage and Operations → Storage. Build with --features distributed for object-store reads.