- What does the summerblue/generator package do for Laravel?
- It is a dev-time CRUD scaffold generator for Laravel 5.3 and later that inspects your database tables and emits Eloquent models, controllers, FormRequests, routes, and Blade views into your application. You can choose Bootstrap or Semantic UI view templates. Generated code lands in your app as ordinary first-party files, so there is no runtime dependency and the package can be removed afterward. It is aimed at internal admin panels, back-office tooling, and boilerplate-heavy prototyping.
- Which Laravel and PHP versions does summerblue/generator support?
- The package advertises Laravel 5.3+, but its last release was in March 2022, which points to Laravel 9-era support in practice. Expect Composer constraint friction on Laravel 10, 11, or 12, and verify PHP 8.2 and 8.3 compatibility in a sandbox before adopting. Pin to a known-good Laravel minor and test schema introspection against your actual database.
- How do I install and run summerblue/generator?
- Install it as a require-dev dependency with Composer, publish the stubs if you want to customize the output, and run the provided Artisan commands per table. Effort is measured in hours, not sprints. Generate into a feature branch and review the result before committing it as first-party code. Because generated files do not depend on the package, you can strip it from your dependencies once scaffolding is done.
- Does summerblue/generator need migrations or a live database?
- The generator works by introspecting database tables, so it needs an accessible schema to read from. Whether it can work from migration files alone is an open question, and schema fidelity for composite keys, enums, JSON columns, and soft deletes is a known risk. Run it against two or three representative tables in a sandbox before pointing it at anything important.
- How does summerblue/generator detect foreign keys and map Eloquent relationships?
- It introspects the database schema and maps foreign keys into Eloquent relationship methods, but the fidelity of that mapping is a noted risk. Non-standard naming, composite keys, polymorphic relations, and pivot tables may produce missing or incomplete relationships. Always diff generated models against your expected relations on a table with real foreign keys before trusting the output.
- Can I customize the generated stubs and templates?
- Yes. Stubs are publishable, which is the main lever for adapting output to your team's conventions. You can add authorization policies, pagination, real validation rules, and tests by editing the stubs your project uses. If your house style diverges heavily, vendor the package or copy the stubs into the repository so generation keeps working even if upstream goes quiet.
- Does summerblue/generator overwrite existing files when regenerating?
- Overwrite and drift behavior against hand-edited files is unverified, and idempotency plus dry-run support are unclear from the available documentation. Treat regeneration as potentially destructive and commit your work before running it. Keep generated code in a feature branch and review diffs carefully. If you need guaranteed --force or dry-run semantics, verify them in a sandbox or fork the package.
- Does summerblue/generator generate policies, validation, pagination, and tests?
- Out of the box the stubs reflect older conventions: no authorization policies, guarded-style mass assignment, thin validation, no pagination, and no generated tests. That is a security and quality gap you must close during stub customization. Add policy checks and real FormRequest rules before exposing generated CRUD controllers to the internet. Test generation is not a provided feature, so plan to write tests yourself.
- Is summerblue/generator safe to use in production?
- It is a dev-only dependency, so it does not sit in your production runtime path and can be removed once code is generated. The generated controllers, however, typically ship without policy or gate checks, so promoting them straight into an internet-exposed admin panel is risky. Review generated code as you would a junior developer's pull request. Add authorization, validation, and pagination before deployment.
- Is summerblue/generator still maintained, and what are the alternatives?
- Maintenance is the biggest concern: there has been no release since March 2022, and Laravel 10, 11, and 12 support would likely require a fork with bumped illuminate constraints and modernized stubs. The MIT license and dev-only nature partially mitigate that risk. Alternatives include actively maintained CRUD generators, or writing a thin in-house Artisan generator if stub divergence exceeds roughly one to two engineer-days. If you adopt it long term, vendor the package so it keeps working after upstream goes quiet.