Merge remote-tracking branch 'old-github/main' into integrate-old-refactors-of-github

docs/SUPABASE_MIGRATION.md

@@ -25,6 +25,7 @@ docker compose up -d
 ### For Supabase CLI Users
 
 **Before** (old way):
+
 ```bash
 cd management-dashboard-web-app
 supabase start
@@ -32,6 +33,7 @@ supabase db reset
 ```
 
 **After** (new way):
+
 ```bash
 # From project root - no need to cd!
 supabase start
@@ -50,23 +52,22 @@ If you have scripts or documentation that reference the old path, update them:
 - ❌ `management-dashboard-web-app/supabase/config.toml`
 - ✅ `supabase/config.toml`
 
-## Backward Compatibility
 
-The old directory (`management-dashboard-web-app/supabase/`) can be kept for reference, but it's no longer used by docker-compose or the Supabase CLI. You can safely remove it after verifying everything works:
+## Current State
 
-```bash
-# After verifying everything works with the new location
-rm -rf management-dashboard-web-app/supabase
-```
+The old directory (`management-dashboard-web-app/supabase/`) has been removed. All Supabase and DB configuration, migrations, and seeds now live only under the project root `supabase/` directory. Docker Compose and the Supabase CLI use root `supabase/` exclusively.
 
 ## Verification
 
-To verify the migration worked:
+To verify the migration:
+
+1. **Check docker-compose paths** (only root supabase should be referenced):
 
-1. **Check docker-compose paths**:
    ```bash
-   grep -r "supabase" docker-compose.yml
-   # Should show: ./supabase/ (not ./management-dashboard-web-app/supabase/)
+   grep "supabase" docker-compose.yml
+   # Should show only ./supabase/ (no management-dashboard-web-app/supabase/)
+
+
    ```
 
 2. **Test Supabase CLI**:
@@ -76,7 +77,8 @@ To verify the migration worked:
    # Should work without needing to cd into management-dashboard-web-app
    ```
 
-3. **Test migrations**:
+1. **Test migrations**:
+
    ```bash
    docker compose up -d
    docker compose logs supabase-migrate
@@ -90,4 +92,3 @@ To verify the migration worked:
 ✅ Easier to share database across services  
 ✅ Better alignment with monorepo best practices  
 ✅ Infrastructure separated from application code  
-