How debdas5110/bank_management_system works
Project type and purpose
• This is a full-stack Bank Management System, with a React/TypeScript frontend and Supabase as a backend-as-a-service (database, auth, file storage). It’s deployed on Vercel for hosting and CDN.
File structure
• Top-level: package.json, Vite config, Tailwind config, supabase/ (config + migrations).
• src/: contains App.tsx, pages/, components/, contexts/, hooks/, integrations/, utils/.
• components/ is subdivided into admin, auth, dashboard, ui.
• integrations/supabase holds the client setup and types.
• supabase/ folder contains the database config and schema migration SQL files.
README for additional insights
• Confirms usage of Vite, React, TypeScript, Tailwind CSS, shadcn-ui.
• Hosted on Vercel, GitHub → Vercel CI/CD pipeline.
• Supabase provides Auth and Postgres DB.
Elements
• Clear labels for each component (e.g., “React App”, “Supabase Auth”, “Postgres DB”)
• Static asset fetch (Browser ← Vercel)
• API/auth calls (Browser ↔ Supabase)
• File uploads (Browser → Supabase Storage)
• Green for BaaS components (Supabase Auth, DB, Storage)
• Orange for external services (Vercel, GitHub)
Detail
• Every Supabase migration and config file as part of the “Database Schema” block
• “src/integrations/supabase/client.ts” as the bridge between UI and backend
• How “contexts” and “hooks” modules manage and expose data across UI layers