Local development

What you get

• Database, workflow engine and edge in one command
• Sign in as any person, role or group
• Public and private routes as in production
• The same environment variables as production
• Real webhooks forwarded to your laptop
• Local secrets kept out of Git

How it works

whisk dev starts PostgreSQL and the Inngest workflow engine in Docker. It adds storage and a key-value store when the app uses them. It then runs the app with the same environment variables it has on Whisk.

A local edge on localhost:3000 behaves like the production edge, which runs on Caddy. It adds the same signed-in headers production sends, for the person, roles and groups you name. Real Whisk sign-in is not used locally, so you can test as anyone.

Secrets for local runs come from a file that Git ignores. whisk dev tunnel forwards the deliveries a deployed app receives from a provider to the app on your laptop, for testing webhook ingress.

Example

A fire protection contractor's developer checks that technicians see only their own inspections while office staff see every one. They start the app as a technician, then as an admin, without creating test accounts.

For your coding agent

whisk dev --as <email> --roles <role> --groups <group> -- npm start
whisk dev tunnel stripe
whisk dev --down

Every flag is in the CLI reference.