Quick Setup CLI

@eep-dev/setup-cli bootstraps EEP configuration and artifacts for both greenfield and existing projects.

Full tutorial (install, both flows, verification, middleware): How to use the Setup CLI ↗

After artifacts are generated, wire your HTTP app: After setup-cli: integration ↗

Core flow

The CLI binary is eep-setup. From the published package: npx @eep-dev/setup-cli@latest <command> (same as eep-setup when the package is on your PATH). Inside the EEP monorepo, use node dist/index.js after npm run build, or npx tsx src/index.ts from packages/@eep-dev/setup-cli — see the full how-to for paths.

# 1) Create setup config (published / global eep-setup)
npx @eep-dev/setup-cli@latest init --preset exchange --out ./eep-setup.json

# Monorepo equivalent (from packages/@eep-dev/setup-cli):
# npx tsx src/index.ts init --preset exchange --out ./eep-setup.json

# 2) Inject into an existing project
eep-setup inject --project /path/to/api --out /path/to/api/eep-setup.json

# 3) Preview artifacts (optional, no writes)
eep-setup apply --config /path/to/api/eep-setup.json --dry-run

# 4) Write artifacts (add --production to block placeholder identities)
eep-setup apply --config /path/to/api/eep-setup.json --output /path/to/api/eep-generated

# 5) Verify and monitor
eep-setup verify --output /path/to/api/eep-generated
eep-setup doctor --output /path/to/api/eep-generated
eep-setup status --output /path/to/api/eep-generated

Security controls

  • Unsafe output paths are blocked by default in apply
  • rotate-secrets supports dual-key windows via EEP_WEBHOOK_SECRET_PREVIOUS
  • verify emits machine and human-readable reports