How umutkarakas34/market-app-laravel-vuejs works
Project type and purpose
• This is a Laravel-powered full-stack web application exposing a RESTful API (“Market-App API”)
• It combines a Vue.js single-page frontend with a Laravel backend, handling user/admin authentication, product management, and order processing
File structure
• Top-level directories:
– app/ (Laravel MVC: Controllers, Models, Middleware, Console, Exceptions, Providers)
– routes/ (defines API routes – api.php – and web routes – web.php)
– resources/js/ (Vue.js app: components, router, bootstrap)
– public/ (compiled assets: app.js, app.css; entry point index.php)
– database/ (migrations, factories, seeders for MySQL)
– config/ (Laravel config for auth, database, services, cache, session, etc.)
• Key config/build: webpack.mix.js for asset compilation, .env for environment variables, composer.json & package.json for dependencies
• Middleware stack enforces authentication (Sanctum), role checks (AdminMiddleware, UserMiddleware), CSRF, cookie encryption, etc.
README for additional insights
• Confirms Laravel + Vue.js + Axios + Sanctum + MySQL
• Lists all API endpoints and their authorization requirements
• Emphasizes simple user vs. admin roles and typical HTTP status error codes
a. Frontend (Vue.js SPA)
– Hosted under public/index.php and served by Laravel’s blade or directly as static assets
– Makes HTTP calls via Axios to /api/* endpoints
b. Backend API (Laravel)
– Public entry point: public/index.php → bootstrap/app.php → HTTP kernel
– Routes → Middleware → Controllers (AuthController, ProductController, OrderController, AdminAuthController)
– Business logic uses Models (User, Admin, Product, Order) and Services (via ServiceProviders)
– Authentication via Laravel Sanctum issuing/revoking tokens
c. Database (MySQL)
– Tables: users, admins, products, orders, personal_access_tokens
– Eloquent ORM handles CRUD from Models to database
d. External services & infrastructure
– File storage (local/public) for any uploads
– Caching, queues, mail services (configured in config/)
– Version control (Git) and build tools (npm, composer)
Architectural patterns and design principles
• MVC pattern in the backend (Controllers → Models → Views or API responses)
• RESTful API design for CRUD operations on Products & Orders
• Single-Page Application (SPA) pattern on the frontend (Vue.js router & components)
• Middleware chain for cross-cutting concerns (Security, Auth, CORS, CSRF)
• Dependency injection and service providers for decoupling
1. Presentation Layer (Client)
– Label “Browser (Vue.js SPA)”
2. Application Layer (Server/API)
– Label “Laravel API Server”
– Show Controllers mapping (AuthController, ProductController, OrderController, AdminAuthController)
– Indicate Laravel ServiceProviders and Eloquent Models
3. Data Layer (Database & Storage)
– Label “MySQL Database” with tables (users, admins, products, orders, tokens)
– Label “File Storage” (local/public)
– Browser → (HTTP/HTTPS) → Laravel API
– Laravel Controllers → (ORM Queries) → MySQL
– Laravel → (Read/Write) → Local Storage