How adatechschool/projet-collectif-microblogging-les_carcajous_sensationnels works
Project Type and Purpose
• Type: Full-stack monolithic web application
• Purpose: A Dockerized micro-blogging platform built with Laravel (PHP) and PostgreSQL, offering user registration/authentication, post creation/editing/deletion, and notifications.
Key Components
A. Developer Environment
• VSCode Dev Container (Docker)
• Docker Compose orchestrating containers
B. Web Application Container
• Nginx (or Apache) / PHP-FPM
• Laravel framework
• Routes (routes/web.php, routes/api.php)
• Controllers (app/Http/Controllers)
• Middleware
• Models & Eloquent ORM (app/Models)
• Views (resources/views) powered by Blade + Tailwind/PostCSS + Vite
• Events & Listeners (app/Events, app/Listeners)
• Notifications (app/Notifications)
• Policies & Authorization (app/Policies)
• Queues & Jobs (config/queue.php – if used)
• Composer dependencies (composer.json/lock)
• Node.js / npm for asset compilation (package.json, vite.config.js, postcss.config.js)
C. Database Container
• PostgreSQL instance
• Schema migrations & seeders (database/migrations, database/seeders)
D. Supporting Services
• pgAdmin (optional, for DB management)
• Redis or cache store (if configured)
• Mail service (SMTP or external via config/mail.php)
• (Optional) Broadcast/WebSocket service (Pusher, Redis + Laravel Echo)
E. Client
• Web browser
• HTTP/HTTPS requests to the web server
• Real-time updates (via AJAX or WebSockets, if implemented)
Relationships & Data Flows
• Developer → VSCode Dev Container → Docker Compose → App & DB Containers
• Client Browser → (HTTP) → Nginx/Apache → Laravel Router → Controllers →
– Read/Write → PostgreSQL
– Publish → Events → Listeners → Notifications (e.g., email, in-app)
– Render → Blade Views + Compiled CSS/JS → Response → Browser
• Laravel Scheduler/Queue Worker → Background Jobs → Database / External APIs
• Asset Pipeline: Laravel Mix / Vite compiles resources/js & resources/css → public/build
Architectural Patterns & Principles
• MVC (Model–View–Controller)
• Layered architecture:
– Presentation (Blade views + assets)
– Application (Controllers, Requests validation)
– Domain (Eloquent Models, Policies)
– Infrastructure (Database, Cache, Queues)
• Event-Driven for decoupling notifications (PostCreated event → SendPostCreatedNotifications listener)
• Dependency Injection (Service Providers: app/Providers)
• Twelve-Factor methodology (env files, separate config, stateless containers)
Final Checklist
[ ] Notes on protocols (HTTP, SQL, WebSockets)
[ ] Callouts for key files/folders: e.g., app/Controllers, resources/views, database/migrations