Perfect_Python500/MineGeo
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix live map community schema and refresh API cache
Some checks failed
Deploy MineGeo to Dokploy / deploy (push) Failing after 3m16s
Details

Browse Source
This commit is contained in:
perfect_python500
2026-10-17 14:17:08 +05:00
parent 8dc8ee3bd7
commit 128caff2a2
2 changed files with 5 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/map-community.md
View File

@@ -10,6 +10,8 @@ Moderators and admins can remove comments directly on map pages or from **Commen
Apply `supabase/migrations/20261017073500_map_community_features.sql` before deploying the application. This adds `map_reactions`, `map_comments`, `community_reports`, and `map_reaction_summary`. All tables enable RLS and restrict access to the server service role. Browser and device-token clients cannot directly read or write these tables. The server routes validate browser sessions, active account status, published-map visibility, and staff roles.
If the server reports `PGRST205` for `public.map_comments`, verify that this migration was applied to the Supabase project configured by the deployed app. Deploying the application source does not apply database migrations. The migration also requests a PostgREST schema-cache reload. If the tables already exist but the cache remains stale, run `NOTIFY pgrst, 'reload schema';` in that project's SQL editor instead of rerunning the table-creation statements.
- `node --import tsx --test tests/community.test.ts` — validation, authentication, moderator authorization, scoped reactions, reporting and review conflicts.
- `node scripts/test-community-sql.mjs` — applies the full migration history in isolated PGlite and verifies constraints, counts, duplicates, deletion, and privileges. Uses the same optional `.data/sql-verification` runtime as the existing SQL suites.