How ashish0070806/dbms-website-project- works
O₂ Fitness is a gym-management terminal for member and staff registration, role-based access, membership operations, attendance, billing, and administration. A typical user registers or logs in through the portal, then reaches a role-appropriate portal; staff and administrators manage gym operations through the terminal. PHP endpoints enforce backend permissions and access MySQL through a shared PDO layer. The README documents training and other terminal capabilities, but the excerpts do not establish all frontend-to-endpoint wiring, so those links are not inferred.
Main entry points: db.php PDO Connection · auth_guard.php Backend RBAC Gateway · index.html Login & Registration · app.js Portal Controller
Components 27
User Portals
- Login & Registration
index.html - Portal Controller
app.js - Member Portal
member.html - Staff Portal
staff.html - Admin Portal
admin.html - Member Controller
member.js
Gym Operations
- Staff Controller
staff.js - Admin Controller
admin.js - Operations Terminal
dashboard.html - Terminal Controller
terminal.js - Member Management API
api/members.php - Membership Plans API
api/plans.php - Attendance API
api/checkin.php - Transactions API
api/transactions.php - Metrics API
api/stats.php - Admin API
api/admin.php
Identity & Access
- Client RBAC Guard
rbac-guard.js - Authentication API
api/login.php - Registration API
api/register.php - Backend RBAC Gateway
api/auth_guard.php
Backend & Data
- PDO Connection
api/db.php - Gym Data Schema
database/o2_gym_os.sql - MySQL Database
Other components
- Visitor
- Member
- Staff
- Administrator
Connections 35
- Visitor → Login & Registration: opens portal
README.md - Member → Login & Registration: signs in
README.md - Staff → Login & Registration: signs in
README.md - Administrator → Login & Registration: signs in
README.md - Login & Registration → Portal Controller: uses controller
README.md - Portal Controller → Authentication API: authenticates
README.md - Portal Controller → Registration API: registers accounts
README.md - Member → Member Portal: uses portal
README.md - Staff → Staff Portal: uses portal
README.md - Administrator → Admin Portal: uses portal
README.md - Member Portal → Client RBAC Guard: guarded by
README.md - Staff Portal → Client RBAC Guard: guarded by
README.md - Admin Portal → Client RBAC Guard: guarded by
README.md - Member Portal → Member Controller: uses controller
README.md - Staff Portal → Staff Controller: uses controller
README.md - Admin Portal → Admin Controller: uses controller
README.md - Staff → Operations Terminal: uses terminal
README.md - Administrator → Operations Terminal: uses terminal
README.md - Operations Terminal → Terminal Controller: uses controller
README.md - Authentication API → PDO Connection: connects through
api/login.php - Registration API → PDO Connection: connects through
api/register.php - Backend RBAC Gateway → PDO Connection: loads connection
api/auth_guard.php - Member Management API → PDO Connection: queries through
api/members.php - Member Management API → Backend RBAC Gateway: checks identity
api/members.php - Membership Plans API → PDO Connection: queries through
api/plans.php - Attendance API → PDO Connection: queries through
api/checkin.php - Attendance API → Backend RBAC Gateway: checks identity
api/checkin.php - Transactions API → PDO Connection: queries through
api/transactions.php - Transactions API → Backend RBAC Gateway: checks identity
api/transactions.php - Metrics API → PDO Connection: queries through
api/stats.php - Metrics API → Backend RBAC Gateway: checks identity
api/stats.php - Admin API → PDO Connection: queries through
api/admin.php - Admin API → Backend RBAC Gateway: checks identity
api/admin.php - PDO Connection → MySQL Database: opens PDO connection
api/db.php - Gym Data Schema → MySQL Database: defines schema
README.md