chore(examples): consistent env files across all examples

Author: andrii-bodnar

examples/ai-tools-example/.env.example

@@ -0,0 +1,3 @@
+# Get your v0 API key here: https://v0.dev/chat/settings/keys
+V0_API_KEY=your_v0_api_key_here
+AI_GATEWAY_API_KEY=your_ai_gateway_api_key_here

examples/ai-tools-example/README.md

@@ -11,11 +11,10 @@ This example demonstrates how to use `@v0-sdk/ai-tools` with the AI SDK to inter
    ```
 
 2. **Set up environment variables:**
-   Create a `.env` file in this directory:
+   Create a `.env.local` file in the root directory:
 
-   ```env
-   V0_API_KEY=your_v0_api_key_here
-   AI_GATEWAY_API_KEY=your_ai_gateway_api_key_here
+   ```bash
+   cp .env.example .env.local
    ```
 
 3. **Get your API keys:**

examples/classic-v0/.env.example

@@ -0,0 +1,2 @@
+# Get your v0 API key here: https://v0.dev/chat/settings/keys
+V0_API_KEY=your_v0_api_key_here

examples/classic-v0/.gitignore

@@ -32,6 +32,7 @@ yarn-error.log*
 
 # env files (can opt-in for committing if needed)
 .env*
+!.env.example
 
 # vercel
 .vercel

examples/classic-v0/README.md

@@ -43,10 +43,10 @@ A faithful recreation of the original v0.dev interface using the v0-sdk. This ex
    pnpm install
    ```
 
-3. Set up environment variables:
+3. Create a `.env.local` file in the root directory:
 
    ```bash
-   export V0_API_KEY=your_api_key_here
+   cp .env.example .env.local
    ```
 
 4. Run the development server:

examples/simple-v0/.env.example

@@ -1,5 +1,5 @@
 # Get your v0 API key here: https://v0.dev/chat/settings/keys
-V0_API_KEY="your_v0_api_key"
+V0_API_KEY=your_v0_api_key_here
 
 # Optional: for rate limiting
 KV_REST_API_URL=your_upstash_redis_rest_url

examples/simple-v0/README.md

@@ -21,12 +21,8 @@ You can deploy your own version of Simple v0 to Vercel with one click:
 2. **Configure environment:**
    Create a `.env.local` file in the root directory:
 
-   ```env
-   V0_API_KEY=your_api_key_here
-
-   # Optional: For rate limiting (if not provided, rate limiting is disabled)
-   KV_REST_API_URL=your_kv_rest_api_url
-   KV_REST_API_TOKEN=your_kv_rest_api_token
+   ```bash
+   cp .env.example .env.local
    ```
 
    - Get your v0 API key from [v0.dev/settings](https://v0.dev/settings)

examples/v0-clone/.env.example

@@ -0,0 +1,14 @@
+# Auth Secret - Generate a random string for production
+# Generate with: openssl rand -base64 32
+# Or visit: https://generate-secret.vercel.app/32
+AUTH_SECRET=your-auth-secret-here
+
+# Database URL - PostgreSQL connection string
+POSTGRES_URL=postgresql://user:password@localhost:5432/v0_clone
+# For Vercel Postgres, use the connection string from your dashboard
+
+# Get your API key from https://v0.dev/chat/settings/keys
+V0_API_KEY=your_v0_api_key_here
+
+# Optional: Use a custom API URL
+# V0_API_URL=http://localhost:3001/v1

examples/v0-clone/.gitignore

@@ -32,6 +32,7 @@ yarn-error.log*
 
 # env files (can opt-in for committing if needed)
 .env*
+!.env.example
 
 # vercel
 .vercel

examples/v0-clone/README.md

@@ -29,23 +29,10 @@ You can deploy your own version of the v0 clone to Vercel with one click:
 
 ### Environment Variables
 
-Create a `.env` file with all required variables:
+Create a `.env.local` file in the root directory:
 
 ```bash
-# Auth Secret - Generate a random string for production
-# Generate with: openssl rand -base64 32
-# Or visit: https://generate-secret.vercel.app/32
-AUTH_SECRET=your-auth-secret-here
-
-# Database URL - PostgreSQL connection string
-POSTGRES_URL=postgresql://user:password@localhost:5432/v0_clone
-# For Vercel Postgres, use the connection string from your dashboard
-
-# Get your API key from https://v0.dev/chat/settings/keys
-V0_API_KEY=your_v0_api_key_here
-
-# Optional: Use a custom API URL
-# V0_API_URL=http://localhost:3001/v1
+cp .env.example .env.local
 ```
 
 ### Database Setup
@@ -116,7 +103,7 @@ This v0 clone includes:
 
 ### Setup
 
-1. Set up all environment variables in `.env`
+1. Set up all environment variables in `.env.local`
 2. Run database migrations with `pnpm db:migrate`
 3. Start the development server with `pnpm dev` or production server with `pnpm start`