kumiko project
kumiko project <subcommand> [<name>]Projections are read-side views derived from the event store. Unlike consumers (which run continuously), a projection can be rebuilt on demand — replay every event, write the read-side from scratch.
Subcommands
Section titled “Subcommands”| Subcommand | What it does |
|---|---|
list | All registered projections + their state |
status <name> | Detail state for one projection |
rebuild <name> | Full rebuild (replays events) + report |
When to rebuild
Section titled “When to rebuild”- After a schema change in the projection’s read-table
- After a bug in the projection’s apply-function — fix code, then rebuild
- After a
kumiko resetif the projection is stateful
kumiko project rebuild users_view# ✓ users_view: 12,847 events, 2,341msRebuilds are read-only against the event store — the source of truth never changes. Worst case after a failed rebuild: re-run it.
Connection
Section titled “Connection”kumiko project reads kumiko.config.ts from the current directory
and connects via DATABASE_URL. Run it from inside an app workspace.
See also
Section titled “See also”kumiko consumer— continuous projections- Event sourcing concept — why projections are rebuildable