Download the PHP package locky42/leopard-admin without Composer
On this page you can find all versions of the php package locky42/leopard-admin. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download locky42/leopard-admin
More information about locky42/leopard-admin
Files in locky42/leopard-admin
Package leopard-admin
Short Description A library for managing the administration panel of a web application.
License MIT
Informations about the package leopard-admin
Leopard Admin Module
locky42/leopard-admin provides admin-domain models, mappings, and controllers on top of leopard-user.
Features
- Base admin models:
Leopard\Admin\Models\BaseAdminUserLeopard\Admin\Models\BaseAdminRoleLeopard\Admin\Models\BaseAdminPermission
- Contract-based model mapping for admin entities
- Doctrine bootstrap integration (
ResolveTargetEntity+ model path registration) - Admin controllers and templates for admin panel flows
Requirements
- PHP
^8.3 doctrine/orm ^3locky42/leopard-userlocky42/leopard-events
Contracts
Leopard\Admin\Contracts\Models\AdminUserInterfaceLeopard\Admin\Contracts\Models\AdminRoleInterfaceLeopard\Admin\Contracts\Models\AdminPermissionInterface
Doctrine Integration
Package bootstrap (packages/leopard-admin/bootstrap.php) does two things:
- Registers resolve-target mappings before EntityManager metadata resolution:
AdminUserInterface -> BaseAdminUserAdminRoleInterface -> BaseAdminRoleAdminPermissionInterface -> BaseAdminPermission
- Adds admin model paths to the current metadata driver via
addPaths([__DIR__ . '/src/Models']).
Quick Start
In application projects, map admin contracts to your app entities (or keep defaults).
ContractFactory::register(...) also synchronizes resolve-target mappings when leopard-doctrine is available.
Controllers
Main controller:
Leopard\Admin\Controllers\AdminController
The controller uses AuthenticationService + AuthorizationService and resolves concrete model classes through ResolveTargetEntityRegistry.
Routing Requirements
For admin module UI to work, your app must provide routes for these controllers:
\Leopard\Admin\Controllers\AdminController\Leopard\Admin\Controllers\AdminAssetsController
You can choose one of these integration strategies:
- Register routes directly to these package controllers.
- Create your own controllers that extend these classes and route to your subclasses.
- Implement equivalent controllers in your app with the required functionality.
If routes for admin pages/assets are missing, admin panel screens and static asset endpoints will not be reachable.
Testing
From repository root:
or
License
MIT
All versions of leopard-admin with dependencies
almasaeed2010/adminlte Version ^3.2
locky42/leopard-events Version ^1.0
locky42/leopard-doctrine Version ^1.0