PHPackages hamza-wakrim/laro-zero - PHPackages - PHPackages [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register) 1. [Directory](/) 2. / 3. [Framework](/categories/framework) 4. / 5. hamza-wakrim/laro-zero ActiveProject[Framework](/categories/framework) hamza-wakrim/laro-zero ====================== The skeleton application for the Laro-zero API framework. v1.0(7mo ago)218MITPHPPHP ^8.2 Since Nov 18Pushed 7mo agoCompare [ Source](https://github.com/Hamza-Wakrim/laro-zero)[ Packagist](https://packagist.org/packages/hamza-wakrim/laro-zero)[ RSS](/packages/hamza-wakrim-laro-zero/feed)WikiDiscussions master Synced 3w ago READMEChangelog (1)Dependencies (5)Versions (2)Used By (0) Laro-Zero ========= [](#laro-zero) A lightweight, API-only Laravel framework fork optimized for building RESTful APIs and microservices. About Laro-Zero --------------- [](#about-laro-zero) Laro-Zero is a streamlined version of Laravel, specifically designed for API development. Built on top of the [hamza-wakrim/api-framework](https://packagist.org/packages/hamza-wakrim/api-framework), it removes all frontend dependencies and view-related components, making it perfect for: - RESTful API development - Microservices architecture - Mobile app backends - Single Page Application (SPA) backends - Headless CMS implementations Features -------- [](#features) - **API-First Design**: Optimized exclusively for API endpoints - **Lightweight**: Removed all frontend build tools and dependencies - **Fast Setup**: Minimal configuration required - **Laravel Compatibility**: Built on Laravel's robust foundation - **Modern PHP**: Requires PHP 8.2 or higher - **Enforced Design Pattern**: Strict Route → Controller → Service → Model architecture Enforced Design Pattern ----------------------- [](#enforced-design-pattern) Laro-Zero **enforces** a strict layered architecture pattern that all developers must follow: ``` Route → Controller → Service → Model ``` ### Pattern Rules [](#pattern-rules) 1. **Routes** (`routes/api.php`) - MUST only call Controllers - NEVER call Services or Models directly - Handle HTTP routing only 2. **Controllers** (`app/Http/Controllers/`) - MUST only call Services - NEVER call Models directly - Handle HTTP concerns (request/response, validation) - All Controllers extend `App\Http\Controllers\Controller` 3. **Services** (`app/Services/`) - Handle ALL business logic - Interact with Models - All Services extend `App\Services\Service` - Must be in `App\Services` namespace and end with `Service` 4. **Models** (`app/Models/`) - Represent database entities only - No business logic - Eloquent ORM models ### Enforcement Mechanisms [](#enforcement-mechanisms) - **Base Service Class**: All services must extend `App\Services\Service` - **Base Controller Class**: Includes `validateService()` method to ensure proper service injection - **Code Structure**: Directory structure and naming conventions enforce the pattern - **Documentation**: Extensive PHPDoc comments explain the pattern ### Example Implementation [](#example-implementation) ``` // routes/api.php Route::get('/examples', [ExamplesController::class, 'index']); // app/Http/Controllers/ExamplesController.php class ExamplesController extends Controller { public function __construct( private ExampleService $exampleService ) { $this->validateService($exampleService); } public function index(): JsonResponse { $users = $this->exampleService->getAllUsers(); return response()->json($users); } } // app/Services/ExampleService.php class ExampleService extends Service { public function getAllUsers() { return Examples::all(); // Interacts with Model } } // app/Models/Examples.php class Examples extends Model { // Model definition only } ``` ### Why This Pattern? [](#why-this-pattern) - **Separation of Concerns**: Each layer has a single responsibility - **Testability**: Easy to mock services in controllers, models in services - **Maintainability**: Business logic is centralized in services - **Scalability**: Easy to add new features following the same pattern - **Consistency**: All code follows the same structure ### Creating New Features [](#creating-new-features) When adding new features, follow these steps: 1. **Create the Model** (if needed) ``` php artisan make:model Product ``` 2. **Create the Service** ``` php artisan make:service ProductService ``` Then extend `App\Services\Service` and add business logic methods. 3. **Create the Controller** ``` php artisan make:controller ProductController ``` Then inject the service in the constructor and call service methods. 4. **Add Routes** ``` Route::prefix('products')->group(function () { Route::get('/', [ProductController::class, 'index']); // ... more routes }); ``` Requirements ------------ [](#requirements) - PHP >= 8.2 - Composer - Node.js (optional, only for development scripts) Installation ------------ [](#installation) ### Via Composer [](#via-composer) ``` composer create-project hamza-wakrim/laro-zero your-project-name ``` ### Manual Installation [](#manual-installation) 1. Clone the repository: ``` git clone https://github.com/hamza-wakrim/laro-zero.git cd laro-zero ``` 2. Install dependencies: ``` composer install ``` 3. Set up environment: ``` cp .env.example .env php artisan key:generate ``` 4. Run migrations: ``` php artisan migrate ``` Quick Start ----------- [](#quick-start) 1. **Start the development server:** ``` php artisan serve ``` 2. **Access the API:** - Health check: `http://localhost:8000/api/health` - API routes: `http://localhost:8000/api/*` 3. **Development mode** (with queue and logs): ``` composer run dev ``` Project Structure ----------------- [](#project-structure) ``` laro-zero/ ├── app/ # Application code │ ├── Http/ │ │ └── Controllers/ # API Controllers (call Services only) │ ├── Services/ # Business logic layer (call Models) │ ├── Models/ # Eloquent Models (database entities) │ └── Providers/ # Service Providers ├── routes/ │ ├── api.php # API routes (call Controllers only) │ └── console.php # Artisan commands ├── config/ # Configuration files ├── database/ # Migrations, factories, seeders └── tests/ # PHPUnit tests ``` **Important**: The directory structure enforces the design pattern: - `routes/api.php` → calls `app/Http/Controllers/` - `app/Http/Controllers/` → calls `app/Services/` - `app/Services/` → calls `app/Models/` API Routes ---------- [](#api-routes) All API routes are defined in `routes/api.php`. By default, routes are prefixed with `/api`. **Remember**: Routes MUST only call Controllers, never Services or Models directly. Example: ``` // ✅ CORRECT: Route calls Controller Route::get('/users', [UserController::class, 'index']); // ❌ WRONG: Route calls Service directly Route::get('/users', function () { return UserService::getAllUsers(); // DON'T DO THIS }); // ❌ WRONG: Route calls Model directly Route::get('/users', function () { return User::all(); // DON'T DO THIS }); ``` Available Commands ------------------ [](#available-commands) - `composer setup` - Install dependencies and set up the project - `composer dev` - Start development server with queue and logs - `composer test` - Run PHPUnit tests - `php artisan serve` - Start the development server - `php artisan migrate` - Run database migrations Configuration ------------- [](#configuration) Key configuration files: - `config/app.php` - Application configuration - `config/database.php` - Database settings - `config/auth.php` - Authentication settings Testing ------- [](#testing) Run tests with: ``` composer test ``` Or directly with PHPUnit: ``` php artisan test ``` Framework --------- [](#framework) This project uses [hamza-wakrim/api-framework](https://packagist.org/packages/hamza-wakrim/api-framework) as its core framework, which is a Laravel fork optimized for API development. Contributing ------------ [](#contributing) Contributions are welcome! Please feel free to submit a Pull Request. License ------- [](#license) The Laro-Zero framework is open-sourced software licensed under the [MIT license](https://opensource.org/licenses/MIT). Support ------- [](#support) For issues and questions, please open an issue on the GitHub repository. ### Health Score 34 — LowBetter than 75% of packages Maintenance64 Regular maintenance activity Popularity9 Limited adoption so far Community6 Small or concentrated contributor base Maturity48 Maturing project, gaining track record Bus Factor1 Top contributor holds 100% of commits — single point of failure How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window. **Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores. **Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement. **Maturity (30%)** — Project age, version count, PHP version support, and release stability. ### Release Activity Cadence Unknown Total 1 Last Release 221d ago ### Community Maintainers ![](https://avatars.githubusercontent.com/u/20706424?v=4)[HamzaWakrim](/maintainers/HamzaWakrim)[@HamzaWakrim](https://github.com/HamzaWakrim) --- Top Contributors [![Hamza-Wakrim](https://avatars.githubusercontent.com/u/57459253?v=4)](https://github.com/Hamza-Wakrim "Hamza-Wakrim (12 commits)") --- Tags apiframeworklaravelrest ### Code Quality TestsPHPUnit ### Embed Badge ![Health badge](/badges/hamza-wakrim-laro-zero/health.svg) ``` [![Health](https://phpackages.com/badges/hamza-wakrim-laro-zero/health.svg)](https://phpackages.com/packages/hamza-wakrim-laro-zero) ``` ### Alternatives [lanin/laravel-api-debugger Easily debug your JSON API. 2311.8M1](/packages/lanin-laravel-api-debugger)[patricksavalle/slim-rest-api Production-grade REST-API App-class for PHP SLIM, in production on https://zaplog.pro (https://api.zaplog.pro/v1) 101.4k](/packages/patricksavalle-slim-rest-api) PHPackages © 2026 [Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)