soc: use a different env template for cloud setups

Author: joshua-journey-apps

.env.cloud.template

@@ -0,0 +1,10 @@
+# Cloud Environment Configuration
+# Copy this template: `cp .env.cloud.template .env.local`
+# Edit .env.local and enter your Supabase and PowerSync project details.
+
+# Supabase Configuration
+VITE_SUPABASE_URL=https://<your-project-id>.supabase.co
+VITE_SUPABASE_ANON_KEY=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.<replace-with-your-anon-key>
+
+# PowerSync Configuration  
+VITE_POWERSYNC_URL=https://<your-project-id>.powersync.journeyapps.com

.env.local.template

@@ -1,10 +1,12 @@
+# Self-hosted Environment Configuration
 # Copy this template: `cp .env.local.template .env.local`
 # Edit .env.local and enter your Supabase and PowerSync project details.
+
 VITE_SUPABASE_URL=http://localhost:54321
 VITE_SUPABASE_ANON_KEY=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJzdXBhYmFzZS1kZW1vIiwicm9sZSI6ImFub24iLCJleHAiOjE5ODM4MTI5OTZ9.CRXP1A7WOeoJeXxjNni43kdQwgnWNReilDMblYTn_I0
 VITE_POWERSYNC_URL=http://localhost:8080
 
-# PowerSync configuration
+# Self-hosted PowerSync Configuration
 PS_POSTGRESQL_URI=postgresql://postgres:postgres@supabase_db_powersync:5432/postgres
 PS_SUPABASE_JWT_SECRET=super-secret-jwt-token-with-at-least-32-characters-long
 PS_API_TOKEN=super-secret

README.md

@@ -143,7 +143,7 @@ Follow the prompts to configure:
 
 First, copy the environment template file:
 ```bash
-cp .env.local.template .env.local
+cp .env.cloud.template .env.local
 ```
 
 Then set the following environment variables in your `.env.local` file: