bash\nSUPABASE_URL=https://nlzvpcyffinqkneptqcx.supabase.co\nSUPABASE_SERVICE_ROLE_KEY=<get-from-supabase-secrets>\n\n\n## Supabase Variables (Already Set - Reference Only)\n\nThese are already in Supabase Edge Function Secrets:\n\nbash\nSUPABASE_URL=https://nl zvpcyffinqkneptqcx.supabase.co\nSUPABASE_ANON_KEY=<anon-key>\nSUPABASE_SERVICE_ROLE_KEY=<service-role-key>\nSUPABASE_DB_URL=<database-url>\nFIREBASE_SERVER_KEY=<firebase-key>\nFIREBASE_SERVICE_ACCOUNT=<firebase-account>\nSLACK_WEBHOOK_URL=<slack-webhook>\n\n\n## How to Get SUPABASE_SERVICE_ROLE_KEY\n\n1. Go to Supabase Dashboard\n2. Project Settings → API\n3. Copy the service_role key (NOT the anon key)\n4. Paste it as SUPABASE_SERVICE_ROLE_KEY in Railway\n\n## Additional Railway Setup\n\n### Create Storage Bucket in Supabase\n\n1. Go to Supabase → Storage\n2. Create new bucket named: renders\n3. Set public access: Yes (so users can download)\n4. Add RLS policy:\n\nsql\n-- Allow public read access to renders\nCREATE POLICY \"Public read renders\" ON storage.objects\n FOR SELECT USING (bucket_id = 'renders');\n\n-- Allow service role to upload\nCREATE POLICY \"Service can upload renders\" ON storage.objects\n FOR INSERT WITH CHECK (bucket_id = 'renders' AND auth.role() = 'service_role');\n\n\n### Install Python Package on Railway\n\nAdd to requirements.txt:\n\nsupabase==2.3.0\n\n\nRailway will auto-install on next deploy.\n