How bigbossa/depmst1 works
Project type and purpose
• This is a monolithic, full-stack PHP web application (“Dormitory Management System”) whose purpose is to allow administrators, staff, and tenants to manage rooms, bills, maintenance, events, reports, user accounts, and related assets (PDFs, images, etc.).
File structure
• Top-level directories:
• admin/ → PHP pages for “admin” workflows (user/room management, billing, utilities, event setup, reports)
• staff/ → PHP pages for “staff” workflows (maintenance, bills, events, reports)
• tenant/ → PHP pages for “tenant” workflows (view bills, request repairs, view reports, dashboard)
• public/ → authentication endpoints (login, register, logout)
• assets/ → static assets (CSS, JS, images) and uploaded Data files (Charter PDFs, Excel)
• config/ → configuration (database connection, session management)
• dormitory_management.sql → database schema dump
• index.php → likely the home page or router entry point
• product-admin-master/ → packaged HTML/CSS/JS admin template (unused or for prototyping)
• Patterns:
• A simple layered pattern: Presentation (PHP + HTML + assets) → Business logic (PHP scripts under each module directory) → Data access (config/database.php) → MySQL database.
• No microservices; a single codebase.
• Assets folder doubles as a file store for Charter documents and static assets.
README for additional insights
• README is empty, so we rely solely on file structure.
Elements
• Labels: “Browser”, “Web Server (PHP)”, “MySQL DB”, “File Storage”
• Browser → Web Server: HTTP Requests
• Web Server → DB: SQL Queries
• Web Server ↔ File Storage: Read/Write Files
• Web Server → Browser: HTML/CSS/JS Response
Detailed guidance
• Break each major module into subcomponents if needed (e.g., Admin → User Management, Room Management, Billing, Utilities, Events, Reports).
• How session management (config/session.php) feeds into each module for access control.
• Important config files (database.php) as the single point of DB configuration.