- What does sbyaute/adminltemaker actually generate for a Laravel application?
- It scaffolds a ready-to-use AdminLTE admin panel, including the layout, sidebar menu, dashboard view, authentication screens, routes, and CRUD controllers built from your Eloquent models. Instead of hand-writing boilerplate views and controllers, you run an Artisan command and get editable files in your own app. Everything it produces is plain Blade and PHP that you own and can modify freely.
- How do I install sbyaute/adminltemaker with Composer?
- Install it with composer require sbyaute/adminltemaker, then publish the package's config, Blade stubs, and AdminLTE front-end assets so they land in your application. After publishing, run the package's scaffolding Artisan command to generate the layout, menu, dashboard, and CRUD resources. Run php artisan list to confirm the exact command signatures for your installed version.
- Which Laravel versions does adminltemaker support?
- Support depends on the Illuminate version constraints declared in the package's composer.json, so check that require block before committing to it. The package relies on standard Blade, routing, and Eloquent APIs rather than exotic internals, which makes it broadly compatible, but you should still verify against your exact Laravel release. If you are on a very new major version, test the scaffold in a throwaway branch first.
- Can adminltemaker build CRUD controllers and routes from my existing Eloquent models?
- Yes. It reads your models and generates resource controllers, routes, and matching Blade views so you get index, create, edit, and delete screens without writing them by hand. The generated controllers use standard Eloquent calls, so you can layer validation, authorization, and relationships on top. Treat the output as a starting point and review it, since generated code cannot know your business rules.
- How do I customize the generated AdminLTE views and layout?
- The package publishes customizable Blade stubs, so you edit the published files rather than the vendor directory. Change the layout, sidebar menu items, branding, and table markup directly in your resources/views directory. Re-publishing with the force flag will overwrite those edits, so keep generated views under version control before you regenerate anything.
- Does adminltemaker integrate with Laravel's existing authentication?
- It is designed to plug into your existing Laravel authentication rather than replace it, generating AdminLTE-styled login and auth views plus routes you can place behind your own middleware. Your existing guards, user model, and password reset flow remain in control. Review the generated route file and confirm the auth middleware matches the guard you actually use.
- What happens if I run the scaffolding command twice, will it overwrite my changes?
- Publishing and generating files can overwrite previously generated views, controllers, and routes, so always commit or stash your work before re-running a scaffold command. Most publish commands prompt before replacing existing files, but generated controllers and route entries may still be rewritten. If you have heavily customized a screen, consider excluding it from regeneration or moving your logic into your own classes.
- How should I secure the generated admin panel in production?
- Wrap the generated admin routes in auth middleware and add authorization gates or policies so only permitted users reach each resource. Use a dedicated guard or admin role rather than exposing the panel to every registered user, and never leave the demo registration or public dashboard route open. Also enforce HTTPS, set APP_DEBUG to false, and review the generated controllers for mass-assignment and validation gaps before going live.
- How do I test the admin panel and CRUD routes that adminltemaker generates?
- Write feature tests that use actingAs with an authorized user and assert successful responses on the generated index, create, and edit routes. Because the controllers are ordinary Laravel resource controllers, you can test them against a test database with factories just like hand-written code. Also add tests for unauthorized access so the middleware around the admin routes stays intact after future regeneration.
- Is adminltemaker a good alternative to Laravel Nova or Filament?
- They solve the problem differently. Nova and Filament are runtime admin frameworks with their own component APIs, while adminltemaker generates static Blade, Bootstrap, and jQuery-based AdminLTE files that you own and can edit without learning a framework. Choose adminltemaker if you want full control over plain Laravel code and a classic AdminLTE look, and choose a runtime framework if you want built-in filters, actions, and widgets maintained for you.