Switching Between two different local Supabase Projects issue
When switching between two Supabase projects using supabase link and supabase unlink, running supabase start for the previously linked project results in an error. It appears the local Supabase environment remains configured for the new project, causing conflicts.
To Reproduce
Steps to reproduce the behavior:
Create two Supabase projects: Set up two separate Supabase projects (e.g., Project A and Project B).
Link to Project A: In your terminal, navigate to your Project A directory and run supabase link --project-ref <Project A ref>.
Start Project A: Run supabase start. This should work correctly.
Link to Project B: Navigate to your Project B directory and run supabase link --project-ref <Project B ref>.
Start Project B: Run supabase start. This should also work correctly.
Unlink Project B: Run supabase unlink.
Attempt to start Project A: Navigate back to your Project A directory and run supabase start. This will likely result in an error.
Expected behavior:
supabase start should successfully start the local Supabase environment for Project A, regardless of previous linking to Project B.
To Reproduce
Steps to reproduce the behavior:
Create two Supabase projects: Set up two separate Supabase projects (e.g., Project A and Project B).
Link to Project A: In your terminal, navigate to your Project A directory and run supabase link --project-ref <Project A ref>.
Start Project A: Run supabase start. This should work correctly.
Link to Project B: Navigate to your Project B directory and run supabase link --project-ref <Project B ref>.
Start Project B: Run supabase start. This should also work correctly.
Unlink Project B: Run supabase unlink.
Attempt to start Project A: Navigate back to your Project A directory and run supabase start. This will likely result in an error.
Expected behavior:
supabase start should successfully start the local Supabase environment for Project A, regardless of previous linking to Project B.
