SUPABASE FORK HOTFIX ⚠️

Critical Information

When working with Supabase in a forked Bolt.new project, you may encounter issues with database connections. This is because the Supabase connection is tied to the original project’s credentials.

The Problem

1. You fork a project that uses Supabase
2. The forked project still tries to use the original project’s Supabase credentials
3. This can lead to:
   • Data leakage
   • Authentication issues
   • Database connection failures

The Solution

1. Create Your Own Supabase Project

• Go to Supabase
• Create a new project
• Get your project credentials

2. Update Environment Variables

After creating your Supabase project:

1. Click “Connect to Supabase” in Bolt.new
2. Follow the connection process
3. This will automatically update your environment variables

3. Run Migrations

Your new Supabase project needs the correct database structure:

1. Look for migration files in /supabase/migrations
2. Apply these migrations to your new project
3. Verify table structure matches the original

Best Practices

1. Always Create a New Project

   • Never use the original project’s credentials
   • Create your own Supabase instance
   • Keep your data separate

2. Check Environment Variables

   • Verify you’re using your own credentials
   • Never commit sensitive information
   • Use the Bolt.new Supabase connection feature

3. Test Thoroughly

   • Verify database connections
   • Test authentication flows
   • Confirm data operations work

Need Help?

If you’re having issues:

1. Check our Advanced Support options
2. Join the Discord community
3. Review the Supabase documentation