How saurabhverma731044-stack/odoo-x-flux works
SubSync has two distinct runtime surfaces in this tree: a standalone browser prototype backed by in-memory sample data, and a Next.js dashboard using Supabase. Users view subscription and payment information through dashboard pages; the prototype additionally exposes role-aware navigation and broader billing, plan, discount, and staff views. The excerpts support the shown page-to-client interactions, but do not establish every query or the full prototype routing. Future enhancements and integrations described in the README are not treated as implemented.
Main entry points: supabase.ts Supabase Client · app.js Role-aware App · app/page.tsx Activity Overview · customers/page.tsx Customer Activity
Components 10
Browser Prototype
- Role-aware App
js/app.js - Sample Records
js/data.js
Next.js Dashboard
- Activity Overview
subsync/app/page.tsx - Customer Activity
subsync/app/customers/page.tsx - Subscriptions
subsync/app/subscriptions/page.tsx - Payments
subsync/app/payments/page.tsx
Data Access
- Supabase Client
subsync/lib/supabase.ts
External Services
- Supabase Database
Other components
- Business User
- Dashboard User
Connections 11
- Business User → Role-aware App: uses
js/app.js - Role-aware App → Sample Records: reads records
js/app.js - Dashboard User → Activity Overview: views dashboard
subsync/app/page.tsx - Dashboard User → Customer Activity: views customers
README.md - Dashboard User → Subscriptions: manages subscriptions
README.md - Dashboard User → Payments: manages payments
README.md - Activity Overview → Supabase Client: queries data
subsync/app/page.tsx - Customer Activity → Supabase Client: queries activity
subsync/app/customers/page.tsx - Subscriptions → Supabase Client: reads and saves
subsync/app/subscriptions/page.tsx - Payments → Supabase Client: loads and inserts
subsync/app/payments/page.tsx - Supabase Client → Supabase Database: connects to
README.md