How amaghe/tenant-trakker-pro works
Project type and purpose
• This is a full-stack, single-page application for property and tenant management with integrated MTN Mobile Money (“MoMo”) payments.
• Frontend: Vite + React + TypeScript + shadcn-ui + Tailwind CSS.
• Backend: Supabase (Postgres DB, Auth, Serverless Functions) plus external MTN MoMo API.
File structure
• Top-level:
• src/ – React application source (pages, components, hooks, services, integrations, lib)
• public/ – static assets and redirect rules
• supabase/ – configuration, database migrations, and serverless functions
• Recognizable patterns:
• “src/pages” & “src/components” → component-based React UI (SPA)
• “src/integrations/supabase” → Supabase client SDK wrapper
• “supabase/functions” → grouped serverless endpoints handling payment requests, callbacks, logging
• “supabase/migrations” → SQL scripts for schema versioning
README for additional insights
• Tech stack confirmed: Vite, TS, React, shadcn-ui, Tailwind
• Deployment: Lovable platform publishes the static frontend and orchestrates Supabase
• Webhook details for MTN MoMo callbacks (URL, secret header, JSON payload fields)
a. Main components
1. Browser (Client SPA)
2. Supabase Auth & Postgres Database
3. Supabase Serverless Functions
4. External MTN MoMo API
5. CI/CD / Migrations pipeline
b. Relationships & interactions
• User → SPA: HTTP/HTTPS, React Router navigates pages (Auth, Dashboard, Payments, Tenants…)
• SPA ↔ Supabase Auth: sign-in/sign-up via Supabase client
• SPA ↔ Supabase Database: CRUD calls through Supabase client for tenants, properties, payments
• SPA → Supabase Function “mtn-momo-request-payment”: initiate MoMo payment
• Function → MTN MoMo API: REST call to request payment
• MTN MoMo API → Function “mtn-momo-callback” (webhook): payment status update
• Function writes status to Supabase DB → Real-time updates push to SPA via Supabase subscriptions
• Debug & logging functions: capture events, errors
c. Architectural patterns & design principles
• SPA client-server pattern
• Serverless microservices (one function per endpoint)
• Event-driven updates (webhooks + real-time DB subscriptions)
• Separation of concerns: UI, data layer, payment orchestration
d. Key technologies & libraries
• Frontend: React, shadcn-ui (UI primitives), Vite, Tailwind CSS
• Data & Auth: @supabase/supabase-js
• Serverless: Supabase Edge Functions (TypeScript)
• External Service: MTN MoMo REST API