canva-multi-env-setup

# Canva Multi-Environment Setup ## Overview Configure Canva Connect API integrations across development, staging, and production. Each environment needs separate OAuth integrations registered in the Canva developer portal with distinct redirect URIs. ## Environment Strategy | Environment | Canva Integration | Redirect URI | Data | |-------------|------------------|--------------|------| | Development | `my-app-dev` | `http://localhost:3000/auth/canva/callback` | Test account | | Staging | `my-app-staging` | `https://staging.myapp.com/auth/canva/callback` | Staging account | | Production | `my-app-prod` | `https://myapp.com/auth/canva/callback` | Real users | **Important:** Register a separate Canva integration per environment. Each gets its own client ID and secret. ## Configuration ```typescript // src/config/canva.ts interface CanvaEnvConfig { clientId: string; clientSecret: string; redirectUri: string; baseUrl: string; // Always api.canva.com — Canva has no sandbox API scopes: string[]; debug: boolean; } const configs: Record<string, CanvaEnvConfig> = { development: { clientId: process.env.CANVA_CLIENT_ID!, clientSecret: process.env.CANVA_CLIENT_SECRET!, redirectUri: 'http://localhost:3000/auth/canva/callback', baseUrl: 'https://api.canva.com/rest/v1', // No sandbox exists scopes: ['design:content:write', 'design:content:read', 'design:meta:read', 'asset:write', 'asset:read'], debug: true, }, staging: { clientId: proce...