18 docs tagged with "supabase"

All authentication paths across the portfolio — token-based admin access (ChurchWiseAI + PewSearch), Supabase Auth (ITW), and team member RBAC invite flow

All tables owned or primarily used by churchwiseai-web — voice agent, chatbot, subscriptions, care, ShareWiseAI, SermonWise, and operational tables

All tables owned by sermon-illustrations/ and SermonWise — illustration content, scripture analysis, theological lenses, lectionary, word studies, and user subscriptions

All tables owned or primarily used by pewsearch/web — church listings, denominations, directory enrichment, and geographic data

Index of all Supabase table documentation — shared production database used by all three active codebases. See sub-docs for per-codebase schema detail.

Decision

Canonical reference for all hosting, domains, environment variables, cron jobs, DNS configuration, voice agent deployment, and monitoring across the ChurchWiseAI portfolio

Diagnose slow Supabase queries with EXPLAIN ANALYZE, identify missing indexes, fix pagination issues (missing .range()), and resolve Supabase advisory warnings

Supabase Auth login/signup flow for ITW, how premium subscription status gates illustration access, and the Stripe checkout + webhook path that unlocks Premium

One-time process to move 9 audited blog articles from static TypeScript into the production Supabase articles table

Verify automated onboarding completed after checkout — check premium_churches record, confirm chatbot/voice provisioning, send magic link, and run manual fallback if webhook failed

Refresh stale Supabase cached aggregates (church stats, denomination counts) when query results are outdated — dir_illustrations is a regular view and never needs refreshing

Apply a schema change to the shared production Supabase database — write migration SQL, verify with dry run, get founder approval for destructive ops, execute, and save to pewsearch/migrations/

Source of truth for all Supabase Auth redirect URLs. Any change to the Supabase dashboard must be reflected here.

Single shared Supabase PostgreSQL instance (dev + prod) — client setup, auth configuration, RLS policies, storage buckets, and safety rules for the shared production database

Correct or update a church's data in the churches table — name, address, phone, website, service times — with safety checks to avoid corrupting the 218K directory

Confirm Supabase automated backups are running — verify backup timestamps, run record count checks on critical tables (unified_rag_content, churches, premium_churches)

What broke