How mouhssinelghazzali/qualtricsapi works
Project type and purpose
• This is a Laravel‐based full‐stack web application scaffold.
• Purpose: Serve HTTP requests (web & API), render Blade views, bundle frontend assets (Vue/JS/CSS), manage persistence (Eloquent ORM), background jobs, cache, and real‐time events.
File structure
• Top‐level “public” folder: entry point (index.php), static assets (css/js/images).
• “app” folder: core PHP code—Controllers (HTTP endpoints), Middleware (authentication, CSRF, etc.), Providers (bootstrap services), Models (app/User.php).
• “routes” folder: route definitions (web.php, api.php, channels.php).
• “resources”: Blade views (resources/views), frontend source (resources/js & components, Sass).
• “config”: environment configuration (DB, cache, mail, services).
• “database”: migrations, factories, seeders.
• “storage”: logs, cache, compiled views, file uploads.
• “bootstrap”: framework bootstrapping & cached files.
• “tests”: automated Feature & Unit tests.
• Asset build: webpack.mix.js, package.json.
Key architecture notes from README
• MVC pattern: routing → controllers → views/models.
• Bundles JS/CSS via Laravel Mix (Webpack).
• Supports queueing, broadcasting, multiple cache/session backends.
Detail
• Service Providers bootstrapping (e.g., AuthServiceProvider)
• Separate environments (.env) feeding into config
• CI/testing (phpunit.xml → tests) and build pipeline (webpack.mix.js)