How tsavou/boldy works
Project Type & Purpose
• Boldy is a monolithic full-stack web application built with Laravel 12 (backend) and Vue 3 + Inertia.js (frontend).
• Its goal is to let freelancers build/verifiy profiles, allow recruiters to search/filter them, and support paid features (boosts, subscriptions) via Stripe.
High-Level Architecture Components
a. Client (Browser)
• Vue 3 single-page‐app served via Inertia.js
• Tailwind CSS for styling
b. Web Server & App Container
• Nginx or built-in HTTP server in Docker Sail
• PHP-FPM running Laravel application
• Inertia bridges HTTP requests to Vue components for SSR/CSR
c. Backend (Laravel)
• Routes (routes/web.php, routes/api.php)
• Controllers (app/Http/Controllers) implementing MVC
• Models & Eloquent ORM (app/Models) interacting with MySQL
• Middleware (app/Http/Middleware) for auth, Inertia handling
• Policies (app/Policies) and Requests (app/Http/Requests) for validation/authorization
• Services & Providers (app/Providers) for bootstrapping features (Stripe, cache, queue)
d. Data Stores
• MySQL (database/migrations, factories, seeders)
• File storage (local & public disk via config/filesystems.php) for media uploads, identity documents
• Cache & session storage (Redis or file based via config/cache.php, config/session.php)
e. External Services
• Stripe API (payment processing & webhooks via Cashier)
• MailPit (local SMTP testing)
• Laravel Cloud (production hosting & CI/CD)
Relationships & Data Flow
• The Browser issues HTTP requests → Nginx/PHP-FPM
• Laravel handles routing: web vs API endpoints
• Controllers invoke Services, Policies, Eloquent Models → MySQL or file storage
• Responses wrapped by Inertia.js and delivered as HTML+props or JSON for the Vue frontend
• For payments, Laravel Cashier communicates with Stripe; webhooks return to Laravel for fulfillment
• Queued jobs (e.g., email notifications) are pushed to Laravel’s queue system and processed by workers
Architectural Patterns & Design Principles
• MVC on the server side
• Inertia.js for “server-driven SPA” pattern (no separate REST API)
• Eloquent ORM for Data Access Layer
• Repository/Factory pattern for test data (Seeders, Factories)
• Policy-based Authorization
• Docker Compose (Laravel Sail) for local environment standardization
• Service-oriented integration with Stripe, MailPit