Deploy Prompts
Prompts for deploying web, admin, and public site applications with pre-flight checks.
Prompts
| # | Prompt | Purpose |
|---|---|---|
| 01 | Deploy Web App | Deploy the main web application |
| 02 | Deploy Admin App | Deploy the admin dashboard |
| 03 | Deploy Public Site | Deploy the public marketing site |
FAQ
What does bun run ci check?
The ci command runs the full pre-flight validation suite in order: lint, typecheck, test, migrations index check, changelog check, and env example check. If any step fails, the process exits with a non-zero code. Always run bun run ci before deploying.
Do I need to run database migrations before deploying?
Migrations are applied to Supabase independently of app deployments (via MCP apply_migration or local migration files). However, bun run migrations:check (included in bun run ci) validates that the migrations index is up to date. If you've added new migration files, run bun run migrations:index first.
What about brand assets?
Brand assets (logos, icons, fonts) are synced from brand/ to apps via bun run brand:sync. This runs automatically as part of bun run dev but should be verified before production deployments if brand assets have changed.
Which apps exist?
| App | Domain | Directory |
|---|---|---|
| Web | app.eko.day | apps/web |
| Admin | admin.eko.day | apps/admin |
| Public | eko.day | apps/public |