- What is laravel-easypanel and how does it compare to Filament or Laravel Nova?
- It is a Livewire-based admin panel and CRUD scaffolding package for Laravel, comparable in spirit to Filament or Nova but focused on generating back-office screens for your Eloquent models inside your own application. Version 2.0.0 adds an ACL with a role manager, Laravel policy authorization, a customizable auth guard, and more flexible Field and Input classes for forms. Unlike a hosted product such as Nova, it hooks directly into your own guards, policies, and migrations, which means you own the security review.
- How do I install laravel-easypanel with Composer?
- Install it with composer require rezaamini-ir/laravel-easypanel, then run the publish commands documented in the README to publish config, views, assets, and migrations. Version 2.0.0 introduces new persistence for roles, permissions, and translations, so run php artisan migrate immediately after publishing. Verify the exact vendor:publish tags in the package documentation, since the release notes do not list them.
- Which Laravel and PHP versions does laravel-easypanel 2.0.0 support?
- The 2.0.0 release notes reviewed do not state Laravel or PHP version constraints, so this is unconfirmed until you check the require block in composer.json on Packagist. Confirm it covers both your current framework version and your next upgrade target before adopting the package. This is the most important check to perform before spending time on a technical spike.
- Is there an upgrade guide from EasyPanel 1.8 to 2.0?
- No upgrade guide is referenced in the 2.0.0 release notes, and the release contains breaking changes including a new admin management strategy and the removal of the TODO feature. Any code, seeders, or tests depending on the old admin model or TODO entities will need rework. Treat the migration as a re-implementation of your admin module rather than a routine composer update.
- Does laravel-easypanel use Laravel policies or its own ACL for authorization?
- Version 2.0.0 introduces both an ACL with a role manager and Laravel policy authorization in generated CRUDs, so two authorization idioms can coexist in one codebase. Where the actual authorization decision is made is not documented in the release notes. If your app already has a Gate or policy convention, test explicitly whether EasyPanel's generated policies compose with yours or override them per resource.
- Can I put the EasyPanel admin area behind its own auth guard and route group?
- Yes, 2.0.0 adds a customizable auth guard, which lets you scope the admin panel to a dedicated guard and route group instead of the default web guard. A separate guard is the recommended way to isolate admin sessions and cookies from your public users. Review the guard and role configuration carefully, because misconfigured guards fail silently and can leave privileged screens reachable.
- How do I customize the fields and inputs in generated EasyPanel CRUDs?
- Version 2.0.0 reworks form generation around new Field and Input classes, described in the release notes as making inputs and fields much more flexible. Whether these classes are a stable public extension API or an internal detail is not stated, so pin the behaviour with tests before depending on it. Treat hand-edited generated CRUDs as disposable and be ready to regenerate them.
- What happened to the TODO feature in EasyPanel 2.0?
- The TODO feature was removed in 2.0.0 according to the release notes, but the notes do not describe the cleanup that comes with the removal. After upgrading, check for leftover routes, tables, menu entries, and generated views, and drop the related tables in a migration if they are no longer used. Confirm nothing in your application still queries those entities before deleting them.
- Does laravel-easypanel support multi-language admin panels and translation management?
- Yes, 2.0.0 adds translation management through the admin GUI, which introduces new persistence for translations plus new cache concerns. Multi-language support also widens your QA matrix, so plan test coverage for every locale you enable. Confirm how the translation cache is invalidated when entries are edited in the panel.
- Is laravel-easypanel production ready and how actively is it maintained?
- The 2.0.0 release has multiple contributors, which is a positive signal, but test coverage, CI status, license, and maintainer cadence could not be verified from the release notes alone. Technical risk is rated medium-high, concentrated in the new privileged security surface and upgrade cost rather than runtime stability. Run a spike that includes a threat review of the ACL, roles, and guard configuration before putting it in front of real admin users.