eropadevcom/admin: a ready Laravel admin instead of building from scratch
Every Laravel project eventually hits the same work: login, roles, CRUD, file uploads, and an audit trail of who changed what. Building that from scratch stretches a “ready product” by weeks.
eropadevcom/admin is that automation layer. It is a universal admin panel with JWT authentication: you require the library in a Laravel app and get a skeleton you can ship on — a shop, a company site with a cabinet, or an internal tool.
Installation is the usual Composer step:
composer require eropadevcom/admin
The package is on Packagist, current release v1.2.2. It needs PHP 8.3, illuminate/support ^13 (Laravel 13), and tymon/jwt-auth. Eropadevcom\Admin\AdminServiceProvider is auto-discovered by Laravel.
What the ready solution gives you: 1. Login and JWT — one session for the panel and a token for a mobile client. 2. Roles and access — RBAC is not designed from a blank page. 3. Config-driven CRUD — describe an entity once and get UI plus API, without a stack of lookalike controllers. 4. Media and audit log — files and activity history already live inside the admin.
The point is simple: the lab uses the package as the first backend automation layer. Instead of rebuilding an admin each time, the team moves straight to the domain logic of the product.
1. Why a package if Laravel already exists
Laravel is a framework, not a finished admin. Auth, policies, resources, uploads, and logs are still separate pieces. eropadevcom/admin folds them into one contour so a project starts as “panel + API”, not an empty artisan skeleton.
2. Install and wire-up
The package installs from Packagist. After composer require, Laravel registers the service provider. Then you publish package config and migrations and set JWT secrets — same as any app using tymon/jwt-auth.
composer require eropadevcom/admin
# Packagist: https://packagist.org/packages/eropadevcom/admin
# PHP ^8.3 • illuminate/support ^13.0 • tymon/jwt-auth ^2.23. CRUD and API without a controller per model
The usual Laravel path is Model, Controller, Request, Resource, routes. In this package a resource is described in config: both the admin screen and the JSON API come from that description. Catalogs, products, leads, and utility entities ship faster.
4. JWT for the panel and a mobile client
An admin is not only a browser UI. JWT lets the same account talk to the API from a phone or a separate frontend. Roles and the audit log stay shared: who signed in, who edited a record, which file was uploaded.