- Is fsi/admin-bundle a Laravel package or a Symfony bundle?
- It is a Symfony bundle, not a Laravel package. It ships a Symfony Bundle class, registers through config/bundles.php, and depends on Symfony HttpKernel, Form, EventDispatcher, and typically Doctrine ORM. Laravel's container, routing, validation stack, and Eloquent are not compatible surfaces.
- Can I use fsi/admin-bundle in a Laravel application?
- No, not without a rewrite. There is no adapter path short of running a hybrid Symfony/Laravel bootstrap, which adds complexity with little benefit. For a Laravel codebase the honest recommendation is to use a Laravel-native admin package instead. If you need this exact bundle, place it inside a Symfony service, never inside the Laravel app.
- How do I install fsi/admin-bundle in a Symfony project?
- Install with composer require fsi/admin-bundle, enable the bundle in config/bundles.php, and define one Admin class per entity with list and form field configuration. Then wire an admin route prefix. The work is configuration-heavy rather than code-heavy, so a one-to-two-day spike on a single entity is realistic.
- Which Symfony and PHP versions does fsi/admin-bundle support?
- Check the bundle's composer.json constraints and match them to your Symfony major version and PHP 8.x version before installing. Do not assume PHP 8.x support; verify the declared supported matrix explicitly. Pin the bundle version and pin Symfony and PHP to that matrix to avoid framework drift.
- Does fsi/admin-bundle use Doctrine ORM or Eloquent?
- It typically depends on Doctrine ORM, and its architecture assumes Symfony Forms, the Symfony Validator, and Doctrine-mapped entities. Eloquent is not a supported persistence layer. Doctrine migrations should remain the schema source of truth, and generated admin configuration should not imply schema changes.
- How does fsi/admin-bundle compare to EasyAdmin and SonataAdmin?
- It occupies the same back-office CRUD and admin-generator category as EasyAdmin and SonataAdmin. EasyAdmin is the default incumbent in the Symfony ecosystem, while fsi/admin-bundle has much lower adoption, around 57 stars and zero dependents. The real question is what capability gap it fills that EasyAdmin or SonataAdmin does not.
- Is fsi/admin-bundle safe for production?
- Treat it as high risk on adoption, longevity, and framework drift. It is single-vendor maintained by FSi with a small community, so escalation is essentially opening a GitHub issue and waiting. It can be acceptable for internal tooling with no SLA, but assign a named owner and a recurring upgrade task. Pin versions and pilot one internal admin surface before expanding.
- How do I build an admin panel for an entity with fsi/admin-bundle?
- Create one Admin class per entity, configure the list and form fields, and wire the admin route prefix. The bundle provides configurable modules, data sources, CRUD resources, filters, forms, actions, and templates. Start with two or three low-risk Doctrine entities behind an admin-only route prefix with its own auth guard.
- How do I test an admin panel built with fsi/admin-bundle?
- Use Symfony's testing tools and functional tests around the admin routes, with Doctrine fixtures for the entities. Verify CRUD list, form, filter, and action behavior through the generated admin classes. There is no Laravel testing integration, so Laravel-side HTTP or feature tests will not exercise the bundle.
- What are the alternatives to fsi/admin-bundle for Laravel developers?
- For Laravel, use a Laravel-native admin panel instead of trying to port a Symfony bundle; the integration cost is a rewrite, not an adapter. For Symfony teams, compare EasyAdmin and SonataAdmin first, since they have broader adoption and ecosystem coverage. Only choose fsi/admin-bundle if it fills a specific gap and you can absorb the maintenance burden.