fix: ensure supabase credentials are persistent on reloads
This commit is contained in:
@@ -80,17 +80,14 @@ You are Bolt, an expert AI assistant and exceptional senior software developer w
|
||||
: ''
|
||||
: ''
|
||||
}
|
||||
IMPORTANT: Create a .env file if it doesnt exist and include the following variables:
|
||||
${
|
||||
supabase?.isConnected &&
|
||||
supabase?.hasSelectedProject &&
|
||||
supabase?.credentials?.supabaseUrl &&
|
||||
supabase?.credentials?.anonKey
|
||||
? `VITE_SUPABASE_URL=${supabase.credentials.supabaseUrl}
|
||||
VITE_SUPABASE_ANON_KEY=${supabase.credentials.anonKey}`
|
||||
: 'SUPABASE_URL=your_supabase_url\nSUPABASE_ANON_KEY=your_supabase_anon_key'
|
||||
}
|
||||
NEVER modify any Supabase configuration or \`.env\` files.
|
||||
IMPORTANT: Create a .env file and ALWAYS populate the variables${
|
||||
supabase?.credentials?.supabaseUrl && supabase?.credentials?.anonKey
|
||||
? ` and include the following variables:
|
||||
VITE_SUPABASE_URL=${supabase.credentials.supabaseUrl}
|
||||
VITE_SUPABASE_ANON_KEY=${supabase.credentials.anonKey}`
|
||||
: '.'
|
||||
}
|
||||
NEVER modify any Supabase configuration or \`.env\` files apart from creating the \`.env\`.
|
||||
|
||||
CRITICAL DATA PRESERVATION AND SAFETY REQUIREMENTS:
|
||||
- DATA INTEGRITY IS THE HIGHEST PRIORITY, users must NEVER lose their data
|
||||
|
||||
Reference in New Issue
Block a user