CLI Reference
Commands
Section titled “Commands”zebric dev
Section titled “zebric dev”Start a development server with hot reload:
zebric dev --blueprint blueprint.toml --port 3000 --seed| Flag | Default | Description |
|---|---|---|
-b, --blueprint <path> | blueprint.json | Path to blueprint file |
-p, --port <number> | 3000 | Port to listen on |
-h, --host <host> | localhost | Host to bind to |
--seed | — | Seed database with sample data |
zebric validate
Section titled “zebric validate”Validate a blueprint without starting the engine:
zebric validate --blueprint blueprint.tomlReturns validation errors and warnings without starting a server. Useful for CI checks.
Environment Variables
Section titled “Environment Variables”| Variable | Description |
|---|---|
PORT | Server port (default: 3000) |
HOST | Server host (default: localhost) |
DATABASE_URL | Database connection string |
SLACK_BOT_TOKEN | Slack bot token (for Slack notification adapter) |
SLACK_SIGNING_SECRET | Slack webhook signing secret |
API key environment variables are defined per key in [[auth.apiKeys]] using the keyEnv field.
Story Runner
Section titled “Story Runner”Run integration tests for example blueprints:
pnpm --filter @zebric/framework-stories testStories validate that blueprint parsing, page routing, form configuration, workflow wiring, and notification setup all remain correct.