Weave Code
Admin Generator Laravel Package
savannabits/admin-generator
Savannabits Admin Generator scaffolds Laravel admin CRUD interfaces from your models and database schema, quickly producing controllers, views, routes, and forms so you can spin up management panels with less boilerplate and customization.
savannabits/admin-generator is a Laravel package that scaffolds admin panels and CRUD interfaces from your existing models and database schema. It automates the repetitive work of building controllers, routes, views, and forms, letting you generate a functional backend in minutes rather than hours.
Designed for rapid prototyping and internal tools, the generator follows Laravel conventions so the produced code stays readable and easy to customize. Generated scaffolds can be adapted freely to match your own validation rules, relationships, and authorization logic.
- Generates CRUD controllers, routes, and Blade views
- Builds forms and listings from model schemas
- Convention-based output that is easy to extend
- Speeds up admin panel and prototype development
Frequently asked questions about Admin Generator
- How do I install savannabits/admin-generator in a Laravel app?
- Install it with Composer using composer require savannabits/admin-generator, then confirm the resolved version actually matches the Laravel major your application runs. Because it is a scaffolding tool you invoke at development time, many teams require it as a dev dependency rather than a production one. The release note itself does not document the install steps, so follow the repository readme for provider registration and any publishable config or stubs instead of assuming the standard flow.
- Which Laravel versions does savannabits/admin-generator support?
- The package versioning is explicitly pegged to Laravel's release cadence: the maintainers state that at every major Laravel release the package will also move to a new major version. That tells you the intent to track framework internals, but it does not tell you the exact illuminate/* and php constraints of any given tag. Read the composer.json at the tag you intend to install before adding it to a project, since that file is the only reliable source for the supported Laravel and PHP versions.
- Does package version 7 mean it is for Laravel 7?
- No. The package major number follows Laravel's major release cadence, but it is not directly readable as a Laravel version, so v7 does not mean Laravel 7 and should not be assumed to mean a specific Laravel major either. Anyone reading ^7.0 next to a laravel/framework constraint can easily misread the compatibility matrix. Publish an internal mapping of package major to Laravel major to PHP version before rolling it out to multiple services.
- What does savannabits/admin-generator actually generate?
- It scaffolds CRUD controllers, models, views, and routes for a back-office admin panel, driven either from your existing database schema or from configuration. The generated output is intended to slot into savannabits/craftable conventions, so it saves the repetitive boilerplate of wiring up index, create, edit, and delete flows. It also ships customizable templates for common admin tasks, which you can adapt to your own UI conventions.
- Do I need savannabits/craftable installed first?
- Yes, in practice. The package is described as a CRUD generator for savannabits/craftable, meaning the code it produces targets that package's models, controllers, and view conventions. Install and configure craftable first, then run the generator so the generated files resolve against an existing foundation. Generating into an application without craftable will likely leave you with broken references.
- Can I generate CRUD from an existing database schema?
- Yes, that is the primary use case. The generator reads your database schema, or a configuration definition, and produces the matching controllers, models, views, and route entries so you do not hand-write them. This is most useful when you already have tables designed and want an admin panel over them quickly. Review the generated code before committing, since scaffolding reflects your schema literally rather than your domain logic.
- Can I customize the templates used by the generator?
- The package includes customizable templates for common admin tasks, so you can adjust the generated output instead of accepting the defaults. Typical Laravel publishing workflows apply, but verify the exact publish tags and stub paths in the repository readme rather than guessing. Customizing stubs early is worthwhile if you have house style rules for controllers or Blade views, because regenerating later will overwrite anything you edited by hand.
- Is savannabits/admin-generator safe to use in production?
- Treat it as a development-time tool that produces code you then own and commit, which limits runtime exposure to whatever it generates. The bigger concern is maintenance: the project sees little activity, so support for newer Laravel majors and timely fixes are not guaranteed. Evaluate it against your current framework version and have a plan to maintain the generated code yourself before adopting it for anything long-lived.
- How do I upgrade savannabits/admin-generator from v6 to v7?
- The v7.0.0 release note announces a versioning policy tied to Laravel majors, not a documented set of code changes, and no upgrade guide or breaking-change changelog is stated. Diff the previous tag against v7.0.0 before touching your Composer constraint; if the diff is empty or trivial, this is a constraint bump rather than a real migration. If the diff is substantial, treat it as a genuine major upgrade with a dedicated branch and a regression pass over your generated admin screens.
- What are the alternatives to savannabits/admin-generator for Laravel admin panels?
- Common alternatives include Filament, Laravel Nova, Backpack for Laravel, and InfyOm generators, each with different trade-offs between opinionated UI, code generation, and licensing. If you are specifically invested in savannabits/craftable, staying with this generator keeps your scaffolding consistent with that stack. If you are not, compare maintenance activity and current Laravel support before committing, since this package is low-activity and its version numbers do not map cleanly to framework versions.
Weaver
How can I help you explore Laravel packages today?