How pdanielfg/tfg-wallamotop works
Project type and purpose
• Wallamotop is a monolithic, full-stack web application offering second-hand motorcycle auctions.
• Backend: Laravel (PHP MVC framework).
• Frontend: Blade templates + Tailwind, Bootstrap, custom CSS/JS.
• Deployed via Docker on an AWS VM, using Docker Compose to orchestrate containers.
Key directories and their roles
• app/ → Laravel application code (Models, Controllers, Middleware).
• resources/ → Blade view templates (HTML + Tailwind/Bootstrap).
• public/ → Static assets (CSS, JS, images, entry point index.php).
• config/ → Laravel configuration (database, mail, cache, queue, services).
• database/ → Migrations, seeders, factories.
• routes/ → API/web routing definitions.
• storage/ → Logs, cache, file uploads.
• stripe/ → Payment secrets for Stripe integration.
• docker-compose.yml & Dockerfile → Container definitions: PHP-FPM, web server, database, cache, queue.
Main components
A. Clients (Web browsers/mobile)
B. Load Balancer (optional AWS ELB)
C. Docker network hosting:
1. Reverse Proxy / Web Server container (Nginx or Apache)
2. PHP-FPM container running Laravel
3. MySQL (or MariaDB) container for relational data
4. Redis container for caching, session storage, queues
5. Queue Worker container (Laravel Horizon / Artisan queue:work)
6. SMTP Mail Server (external or containerized)
7. Stripe Payment API (external service)
8. AWS EBS or local filesystem for uploads
Component relationships and data flows
• Clients → HTTP/HTTPS → Load Balancer → Nginx
• Nginx → passes PHP requests to PHP-FPM → Laravel routing → Controllers → Models → MySQL (CRUD)
• Laravel → writes cache/sessions/jobs to Redis
• Queue Worker → pulls jobs from Redis → sends emails via SMTP or processes long tasks
• Laravel → invokes Stripe API for payment processing (uses keys from stripe/secrets.php)
• Laravel → serves static assets directly from public/ (optionally via CDN)
• Uploads (moto images) → stored in storage/app/public → symlinked to public/storage
Architectural patterns and principles
• MVC (Model-View-Controller) in Laravel.
• Containerized micro-services via Docker Compose (not true microservices but isolated services).
• Asynchronous job queues for email verification, notifications, auction closing logic.
• Role-based access control (middleware guards Admin vs User).
• Real-time countdown relies on front-end JS polling or websockets (could be a future enhancement).
Detailed elements
• Clients → ELB (if used) → Nginx container
• Nginx → PHP-FPM → Laravel MVC
• Laravel → MySQL (Eloquent ORM)
• Laravel → Redis (cache/session/queue)
• Queue Worker → Redis → SMTP mail server
• Laravel → Stripe API (HTTPS)
• Public/storage mount for uploaded images
• Docker Compose YAML as orchestration layer