How cogover/custom-backend-module-starter-project works
This is a minimal Cogover custom-backend starter, with local tooling for exercising the same project handler and record triggers used by Cogover’s runtime. The documented workflow is to implement a module in src/, load it with the local CLI, test routes or trigger runs through the local HTTP server, then publish and activate it with Cogover’s CLI. The src/ implementation is absent from the tree, so its internal behavior is not expanded; trigger-runner relationships reflect the sampled source and README.
Main entry points: local-server.ts Local HTTP server · cli.ts Local CLI · trigger-runner.ts Trigger runner · src Project module
Components 11
Backend module
- Project module
src - Route handler
src - Trigger definitions
src
Local runner
- Local CLI
local/cli.ts - Local HTTP server
local/local-server.ts - Trigger runner
local/trigger-runner.ts
Other components
- Developer
- HTTP client
- Development Session
- Cogover Runtime
- Cogover Dev CLI
Connections 13
- Developer → Project module: implements
- Developer → Local CLI: starts
- Local CLI → Project module: loads
- Local CLI → Local HTTP server: starts
- HTTP client → Local HTTP server: sends requests
- Local HTTP server → Route handler: invokes routes
- Local HTTP server → Trigger runner: dispatches trigger
- Local HTTP server → Trigger definitions: lists triggers
- Trigger runner → Development Session: reads records
- Trigger runner → Trigger definitions: runs handler
- Cogover Runtime → Project module: runs published module
- Developer → Cogover Dev CLI: publishes and activates
- Cogover Dev CLI → Cogover Runtime: publishes version