Local Supabase Server

Why?

When working on a feature branch, we can't change the schema of staging/dev db as others testing or working on other branches might face conflicts. To avoid this issue, when working on a feature branch which requires changing schema of the db, local db server MUST BE USED. Once the feature branch is merged, staging/dev db should be migrated accordingly.

Explained in detail here

Setup

1. Install Docker/Docker Desktop
2. Install Supabase CLI (not the npm one)
3. npm install -g env-cmd
4. ask for .env file and place it into code\backend\mb-supabase
5. cd code\backend\mb-supabase
6. env-cmd supabase start
7. replace the value of api url and anon key shown in the terminal, to the value of SUPABASE_URL and SUPABASE_KEY respectively in code\presentation\mb-client\.env.development
8. make sure to replace 127.0.0.1 to your local ip in SUPABASE_URL in code\presentation\mb-client\.env.development
9. mb-client should now connect to local db instead of staging db

How to change Schema

• Follow this guide to create migration for your db
• dont forget to update the seed too using supabase db dump -f supabase/seed.sql --data-only --local

---

some useful commands

# links remote to local
supabase link

# pulls remote migrations
supabase db pull

# fetches data form remote and saves into seed.sql
supabase db dump -f supabase/seed.sql --data-only

# starts supabase with .env environment
env-cmd supabase start

# resets database using migrations + seed
supabase db reset

# generates types for client
supabase gen types typescript --linked > ..\..\presentation\mb-client\src\api\supabase\types.ts