How loadpartner/tms works
Project type and purpose
• This is a full-stack, monolithic web application: an open-source Transportation Management System (TMS) for freight brokers.
• Backend: Laravel PHP application structured around Controllers, Actions, Services, Models, Events/Listeners and Policies.
• Frontend: React components served via Inertia.js and built with Vite and Tailwind CSS.
• It supports user authentication, role/permission checks, shipments/state transitions, document generation, email, subscription billing, and integration settings.
File structure
• Top-level directories:
• app/ – Laravel domain logic (Actions, Models, Controllers, Services, States, Events, Listeners, Policies)
• resources/js/ – React components, pages, layouts, hooks under Inertia
• resources/views/ – Blade templates for emails and Inertia entry point
• config/, bootstrap/, routes/ – standard Laravel MVC setup
• database/ – migrations, factories, seeders (SQLite used in dev or MySQL/Postgres in prod)
• .docker/, .do/, Dockerfile.*, docker-compose.yml – containers for nginx, PHP-FPM, queue workers, database, mailpit, localstack S3, etc.
• tests/ – PHPUnit and Pest tests for features and units.
README for additional insights
• Tech stack: Laravel + Inertia.js + React
• Docker/Sail configuration includes:
• PHP container with composer, artisan, supervisor for queue workers
• Nginx as reverse proxy/web server
• Database service (SQLite by default, but Docker Compose can spin up MySQL/Postgres)
• Redis (queue backend), Mailpit (SMTP dev mail catcher), Localstack (S3 emulation)
• Integration points: FMCSA DOT lookup, AWS S3, Stripe billing portal.
Details
• Middleware cross-cutting (authentication, subscription checks, Inertia)
• Build/deploy tools: Vite build, Docker images, Supervisor for queues, Sail for local dev