Improve CLI Setup & Cloudflare Resource Namespacing to Avoid Conflicts

[ahaywood]

Is your request related to a problem? Please describe.

The current create-emdash setup CLI is wonderfully minimal, but it abstracts away key Cloudflare configurations, creating friction when deploying and managing projects:

1. Deployment Command Ambiguity: Developers familiar with Cloudflare Workers naturally run npx wrangler deploy, which fails or behaves unexpectedly because EmDash relies on its own pnpm run deploy script.
2. Resource Naming Conflicts: The setup process creates default/hardcoded resource bindings for Cloudflare D1, KV, and R2 (e.g., EMDASH_DB, MEDIA, etc.). While this works for a user's first EmDash site, attempting to deploy a second EmDash site on the same Cloudflare account results in binding collisions, overwritten databases, or broken deployments.

Describe the solution you'd like

We would love to see the CLI setup process improved in two areas: interactive resource namespacing during initialization and clearer post-setup terminal output.

1. Project-Specific Binding Namespacing

During CLI setup (or via prompt when choosing Cloudflare Workers), ask or automatically generate unique names for Cloudflare resources based on the project name:

• D1 Database: emdash-{project_name}-db
• R2 Bucket: emdash-{project_name}-media
• KV Namespace: emdash-{project_name}-cache

2. Enhanced Terminal Output & Next Steps

Following the example of frameworks like vinext, the CLI output should explicitly outline the exact commands run, the deployment scripts expected, and step-by-step instructions for provisioning Cloudflare resources if manual binding is required.

Example Proposed Output:

Success! Created test-www at /path/to/test-www

Next steps for Cloudflare Workers deployment:
 1. Provision Cloudflare resources with unique names:
    - npx wrangler d1 create test-www-db
    - npx wrangler r2 bucket create test-www-media
    - npx wrangler kv namespace create test-www-kv

 2. Ensure your wrangler.jsonc contains these binding IDs.

Available scripts:
  pnpm dev        Start local dev server
  pnpm run build  Build production bundle
  pnpm run deploy Deploy to Cloudflare Workers (Note: Use this instead of 'wrangler deploy')