How apexpredator20050904/cblrep works
CBLREP is a barangay resource-exchange portal: members use the Flutter app to post offers or needs and negotiate two-sided exchanges; municipal staff use a React console to verify residents and moderate activity. Both clients reach the Laravel API, which routes requests to domain controllers and persists portal state. The README documents the mobile/API and console/API connections; source-index references and excerpts support the controller, model, and notification links. Mobile implementation details were not sampled, so its internal stages are left aggregated.
Main entry points: api.php API routes · ExchangeController.php Barter workflow · AdminTwoFactorController.php Admin 2FA · NotificationService.php Notifications
Components 20
Portal clients
- Member app
mobile - Admin console
frontend/src/App.jsx
API workflows
- API routes
backend/routes/api.php - Sign-in and 2FA
backend/app/Http/Controllers/Api/AuthController.php - Admin 2FA
backend/app/Http/Controllers/Api/AdminTwoFactorController.php - Listing management
backend/app/Http/Controllers/Api/ListingController.php - Barter workflow
backend/app/Http/Controllers/Api/ExchangeController.php - Admin operations
backend/app/Http/Controllers/Api/AdminPortalController.php - Resident approvals
backend/app/Http/Controllers/Api/AdminApprovalController.php - Admin capabilities
backend/app/Http/Controllers/Api
Portal domain
- Listings
backend/app/Models/Resource.php - Exchange records
backend/app/Models/Exchange.php - Member accounts
backend/app/Models/User.php - Audit trail
backend/app/Models/AuditLog.php - MariaDB
backend/config/database.php
Member services
- Notifications
backend/app/Services/NotificationService.php - Push delivery
backend/app/Services/PushService.php - TOTP support
backend/app/Support/TotpService.php
Other components
- Community members
- Municipal admins
Connections 27
- Community members → Member app: uses
README.md - Municipal admins → Admin console: uses
README.md - Member app → API routes: requests API
README.md - Admin console → API routes: requests API
README.md - API routes → Sign-in and 2FA: routes to
backend/routes/api.php - API routes → Listing management: routes to
backend/routes/api.php - API routes → Barter workflow: routes to
backend/routes/api.php - API routes → Admin operations: routes to
backend/routes/api.php - API routes → Resident approvals: routes to
backend/routes/api.php - API routes → Admin 2FA: routes to
backend/routes/api.php - Sign-in and 2FA → Member accounts: uses accounts
backend/app/Http/Controllers/Api/AuthController.php - Sign-in and 2FA → Admin 2FA: delegates 2FA
backend/app/Http/Controllers/Api/AuthController.php - Admin 2FA → TOTP support: verifies codes
backend/app/Http/Controllers/Api/AdminTwoFactorController.php - Admin 2FA → Member accounts: checks accounts
backend/app/Http/Controllers/Api/AdminTwoFactorController.php - Listing management → Listings: manages listings
backend/app/Http/Controllers/Api/ListingController.php - Barter workflow → Exchange records: manages trades
backend/app/Http/Controllers/Api/ExchangeController.php - Barter workflow → Listings: checks listings
backend/app/Http/Controllers/Api/ExchangeController.php - Barter workflow → Notifications: notifies parties
backend/app/Http/Controllers/Api/ExchangeController.php - Admin operations → Audit trail: reads audit
backend/app/Http/Controllers/Api/AdminPortalController.php - Resident approvals → Audit trail: records decisions
backend/app/Http/Controllers/Api/AdminApprovalController.php - Resident approvals → Notifications: notifies members
backend/app/Http/Controllers/Api/AdminApprovalController.php - Notifications → Push delivery: dispatches push
backend/app/Services/NotificationService.php - Notifications → Member accounts: checks preferences
backend/app/Services/NotificationService.php - Admin capabilities → API routes: routes documented
backend/routes/api.php - Listings → MariaDB: persists
- Exchange records → MariaDB: persists
- Member accounts → MariaDB: persists