Project Structure

High-Level Overview

Exowpee follows a monorepo architecture where the core Laravel application lives alongside domain-specific packages in the packages/ directory.

exowpee-laravel/
├── app/                    # Core Laravel application
├── packages/               # Domain packages (the heart of business logic)
│   ├── catalog/            # Products, categories, inventory, purchases
│   ├── customer/           # Customer management
│   ├── iam/                # Identity, authentication, roles, permissions
│   ├── ledger/             # Accounting & financial entries
│   ├── notification/       # Email notifications (invitations, onboarding, verification)
│   ├── order/              # Order lifecycle & payments
│   ├── shared/             # Common utilities, traits, base classes
│   └── team/               # Companies, organizations, members
├── database/               # Migrations, seeders, factories
├── routes/                 # API route definitions
├── config/                 # Configuration files
├── tests/                  # PHPUnit tests
├── docs/                   # This documentation (Mintlify)
├── docker/                 # Docker configuration
└── public/                 # Web root

The folders exowpee-core/ and layers/ are legacy code from a previous architecture. All active business logic has been moved to packages/. Do not modify files in these deprecated directories.

The `app/` Directory

The app/ directory is minimal — it only contains application-level middleware and service providers. All business logic lives in packages/.

app/
├── Http/
│   └── Middleware/              # Request middleware pipeline
│       ├── ForceJsonResponse    # Forces Accept: application/json on all requests
│       └── SetLocale            # Sets app language from X-Language header
└── Providers/                   # Service providers
    ├── AppServiceProvider       # Registers Scramble API docs config
    └── TelescopeServiceProvider # Configures Laravel Telescope debugging

The app/ directory does not contain Events, Models, Services, Traits, Helpers, Casts, or Console directories. All domain logic, helpers, traits, and models live inside the packages/ directory.

The `packages/` Directory

Each package is a self-contained Laravel package with its own models, controllers, services, migrations, routes, and policies.

Standard package structure

Every package follows this layout:

packages/{name}/
├── src/
│   ├── Providers/          # Service provider (registers routes, policies, migrations)
│   ├── Http/
│   │   ├── Controllers/    # API controllers
│   │   ├── Requests/       # Form request validation
│   │   └── Resources/      # API resource transformers
│   │   └── routes.php      # Package API routes
│   ├── Models/             # Eloquent models
│   ├── Services/           # Business logic
│   ├── Policies/           # Authorization policies
│   ├── Enums/              # PHP 8.1+ enums
│   ├── Contracts/          # Interfaces for inter-package communication
│   ├── Traits/             # Package-specific traits
│   └── Rules/              # Custom validation rules
├── database/
│   └── migrations/         # Package-specific database migrations
├── lang/                   # Translation files (en, fr)
├── config/                 # Package configuration (if needed)
└── composer.json           # Package dependencies

Package inventory

Package	Models	Controllers	Services	Policies	Migrations
`catalog`	21+	14+	10+	18	30+
`iam`	5	4	5	6	10+
`team`	5	4+	8	7	10+
`order`	4	2+	8	5	10+
`ledger`	6	1+	2+	-	5+
`customer`	1	1+	1+	1	5+
`notification`	-	-	1	-	-
`shared`	1+	1+	1+	-	2+

The `routes/` Directory

routes/
├── api.php       # Application-level API routes (constants, pricing plans, payment methods)
├── web.php       # Web routes (minimal)
├── channels.php  # Broadcasting channel authorization
└── console.php   # Console command scheduling

Most API routes are defined inside packages at packages/{name}/src/Http/routes.php, not in routes/api.php. The main routes/api.php only contains routes that don’t belong to a specific package.

The `database/` Directory

database/
├── migrations/       # 6 application-level migrations (cache, jobs, telescope)
├── seeders/          # Database seeders
│   ├── DatabaseSeeder.php
│   ├── PaymentMethodSeeder.php
│   └── PricingPlanSeeder.php
├── factories/        # Model factories for testing
└── procedures/       # PostgreSQL stored procedures

Package-specific migrations live in packages/{name}/database/migrations/.

The `config/` Directory

File	Purpose
`app.php`	Application name, timezone, locale, service providers
`auth.php`	Authentication guards (JWT, Sanctum, Agent)
`broadcasting.php`	WebSocket broadcasting (Reverb)
`database.php`	PostgreSQL connection settings
`cors.php`	Cross-Origin Resource Sharing rules
`sanctum.php`	API token authentication
`reverb.php`	Reverb WebSocket server config
`scramble.php`	API documentation auto-generation
`telescope.php`	Laravel Telescope debugging tool
`queue.php`	Queue driver and connections

Key files at root

File	Purpose
`composer.json`	PHP dependencies + monorepo package paths
`.env.example`	Environment variable template
`docker-compose.yml`	Docker service definitions
`Dockerfile`	PHP 8.4-FPM container image
`nginx.conf`	Nginx reverse proxy configuration
`Makefile`	Developer convenience commands
`openapi.json`	OpenAPI 3.0 specification
`pint.json`	PHP code style rules (Laravel Pint)
`phpunit.xml`	Test configuration

What’s deprecated

Directory	Was	Status
`exowpee-core/`	TypeScript core definitions	Deprecated — unused
`layers/`	Old domain-driven layered architecture	Deprecated — migrated to `packages/`

Getting started

Architecture

Developer guide

Operations

More

Project Structure

High-Level Overview

The `app/` Directory

The `packages/` Directory

Standard package structure

Package inventory

The `routes/` Directory

The `database/` Directory

The `config/` Directory

Key files at root

What’s deprecated

​High-Level Overview

​The app/ Directory

​The packages/ Directory

​Standard package structure

​Package inventory

​The routes/ Directory

​The database/ Directory

​The config/ Directory

​Key files at root

​What’s deprecated

High-Level Overview

The `app/` Directory

The `packages/` Directory

Standard package structure

Package inventory

The `routes/` Directory

The `database/` Directory

The `config/` Directory

Key files at root

What’s deprecated