How yassine-dox/internship-management works
Project type and purpose
• This is a classic full-stack web application for managing volunteer registrations and internship stages.
• It uses PHP for server-side logic, MySQL for data storage, and Bootstrap 5 + HTML/CSS for the UI.
File structure
• Top-level PHP pages (login.php, rejistre.php, demande.php, etc.) serve as controllers and views.
• coon.php holds the database connection logic.
• infosession.php and deconnexion.php manage session state.
• bootstrap-5.3.3-dist contains all static CSS/JS assets for styling and front-end behaviors.
• There is no separate “models” folder, but the database tables implied by the README represent the data layer.
Extract README insights
• The app supports: user signup/login, city/association management, stage scheduling, and volunteer “demande_inscription.”
• Database schema has five tables (volontaire, ville, association, stage, demande_inscription) with clear foreign-key relationships.
• The stack is PHP/MySQL/Bootstrap, served over Apache (implied via XAMPP/WAMP).
Main components
a. Presentation Layer (Client Browser + Bootstrap Assets)
• HTML/CSS/JS files (delivered via Apache)
• bootstrap-5.3.3-dist/js & css
b. Web Server / Application Layer
• Apache + PHP runtime
• PHP scripts:
– coon.php (DB connector)
– login.php / rejistre.php (authentication)
– demande.php / infosession.php / deconnexion.php (session & request handling)
– navbare.php (UI fragment)
c. Data Layer
• MySQL database with five tables and relationships:
– volontaire ⇄ ville (Many-to-One)
– stage ⇄ association (Many-to-One)
– demande_inscription ⇄ volontaire & stage (Many-to-One on both)
d. (External) Infrastructure
• XAMPP/WAMP for local dev
• Potential future integration: email server for notifications
Relationships and interactions
• Browser issues HTTP requests (GET/POST) to PHP endpoints.
• PHP scripts authenticate sessions, validate input, and call coon.php to query or update MySQL.
• Query results are rendered into HTML templates (with navbare.php included).
• State changes (new volunteer sign-up, new demande_inscription) persist in the MySQL data layer.
Architectural patterns and design principles
• MVC-style:
• View = PHP pages + Bootstrap templates
• Controller = PHP scripts handling request logic
• Model = MySQL tables accessed via coon.php
• Separation of concerns: front-end assets in bootstrap-5.3.3-dist, back-end in root PHP files
• Session management for authentication