- What does LyssalAdminBundle do for a Symfony application?
- LyssalAdminBundle is a Symfony bundle that adds a configurable administration backend to your application. It maps Doctrine entities to ready-to-use CRUD screens with default list, form, and detail views, and organises them in a dashboard with configurable menus. The goal is to cut the boilerplate normally required to build internal content management screens.
- How do I install LyssalAdminBundle with Composer?
- Install it with Composer using the package name lyssal/admin-bundle. You then register the bundle in your Symfony application's bundle configuration and enable the admin routing. Because configuration options change between releases, always check the repository README for the exact registration snippet and required Symfony and Doctrine dependencies.
- Does LyssalAdminBundle work with Laravel?
- No. LyssalAdminBundle is a Symfony bundle, not a Laravel package, so it depends on Symfony's bundle system, service container, routing, and typically Twig templating. It will not install or run inside a Laravel application without extensive rework. For Laravel you should look at packages such as Laravel Nova, Filament, or Backpack instead.
- Which Symfony and Doctrine versions does this admin bundle support?
- The bundle is built around native Symfony integration and Doctrine entities, but supported Symfony and Doctrine versions depend on the release you install. Check the composer.json constraints and the changelog in the GitHub repository before upgrading your framework. Pinning to a compatible tagged release is the safest approach for existing projects.
- How do I register a Doctrine entity as a CRUD screen?
- Screens are declared through the bundle configuration, where you point the admin layer at each Doctrine entity you want to manage. Once an entity is registered, the bundle provides default list, form, and detail views without you writing controllers. You can then refine fields, labels, and behaviour per resource through configuration and template overrides.
- Can I customise the default list, form, and detail templates?
- Yes. The bundle ships default views but is designed to be extensible, so you can override its templates and services to match your own design or add custom screens. Template overriding follows the usual Symfony bundle override conventions. Custom services let you extend behaviour beyond what the default configuration exposes.
- How do I configure the admin dashboard menu and navigation?
- Menus and dashboard navigation are configurable, letting you group CRUD screens into a structure that matches your content model. Entries are defined in the bundle configuration alongside your entity registrations. This keeps routing and navigation in one place rather than scattered across controllers and templates.
- How do I restrict access to the admin backend?
- Access control is handled by Symfony's own security component rather than by the bundle itself, so you protect the admin routes with firewalls and role checks in security.yaml. Make sure every generated admin route sits behind an authenticated firewall before exposing the backend. Restricting by role is strongly recommended even on internal or staging environments.
- Is LyssalAdminBundle ready for production use?
- It is a developer-oriented bundle that generates working CRUD screens quickly, which makes it reasonable for internal tools and back-office panels. Before production, review the release history and test each screen against your real data and permissions, since default views may need tightening for large datasets. Also confirm the project is actively maintained for the Symfony version you deploy.
- What are the alternatives to LyssalAdminBundle for a Symfony admin panel?
- Popular options include EasyAdmin, SonataAdminBundle, and custom Symfony controllers with your own templates. EasyAdmin is the closest match for entity-driven CRUD with minimal configuration, while Sonata suits larger, more structured backends. LyssalAdminBundle is worth considering if you want a lightweight, configurable admin layer that you can extend with your own services and templates.