- Is runroom-packages/user-bundle a Laravel package?
- No. runroom-packages/user-bundle is a Symfony bundle, structured per Symfony bundle conventions, and its description explicitly targets Sonata admin user management. It ships no Laravel service provider, facade, Eloquent model, or publishable config. For a Laravel-standardized codebase, architecture fit is effectively zero.
- Can I use RunroomUserBundle in a Laravel application with Eloquent?
- Not realistically. The bundle relies on Symfony's dependency injection container, bundle extension classes, Doctrine entity mapping, Symfony Security, and Twig template overrides, none of which port to Laravel without a bespoke bridge. Building that bridge would cost more than reimplementing admin user CRUD on Laravel-native primitives. Treat this as not applicable rather than low compatibility.
- What does RunroomUserBundle actually do?
- It provides reusable user entities, services, and configuration for accounts, authentication, and profiles, packaged as a thin opinionated layer over Sonata Admin's user management. The goal is consistent, maintainable user handling in Symfony applications with less boilerplate. It is not a standalone authentication framework and does not replace Symfony Security.
- Which Symfony, PHP, Sonata Admin and Doctrine versions does RunroomUserBundle support?
- The available evaluation material does not state supported version ranges, so you must read the current composer.json before assuming anything. Pay close attention to the Symfony, Sonata Admin, Doctrine ORM, and PHP constraints, because each one is a compatibility link you do not control. If the ranges are loose or unpinned, assume breakage risk on upgrades.
- Does RunroomUserBundle require FOSUserBundle?
- Sonata Admin's user management historically wraps FOSUserBundle, and this bundle sits on top of that stack, so FOSUserBundle is a likely hard dependency rather than an optional one. FOSUserBundle is archived upstream, which means no security patches. Confirm in composer.json whether it is still required or has been replaced by Symfony's native user provider.
- How do I install and configure RunroomUserBundle?
- Installation is through Composer inside a Symfony application, followed by enabling the bundle in the kernel or bundles.php and wiring security, Doctrine mapping, and Twig overrides. There is no vendor:publish step and no Laravel-style config file, because configuration flows through Symfony's bundle extension. Verify that the package is published on Packagist with real release tags rather than only being consumable from a VCS repository.
- What are the Laravel alternatives for admin user management?
- Filament, Jetstream, and Breeze cover most admin user CRUD, authentication, and profile needs directly on Laravel primitives. For stricter requirements, a small custom guard and policy layer is often enough and is typically a two-week build. The burden of proof should sit with adopting a dependency, not with avoiding one.
- Is RunroomUserBundle safe to use in production?
- The adoption signals are uniformly negative: zero stars, zero dependents, a composite score of zero, and no ecosystem pull. Zero dependents on an authentication-related package is the loudest warning, since auth is a domain where teams almost always pull a dependency. The exposed surface covers credential storage, password reset flows, role escalation, and admin session handling, and there is no upstream patch path or CVE-watching community. The MIT license is the only clean signal.
- Does RunroomUserBundle provide anything beyond sonata-project/user-bundle?
- Probably not much beyond internal Runroom conventions. The maintained first-party sonata-project/user-bundle covers the same ground with an actual maintainer team behind it. If your estate is genuinely Symfony plus Sonata Admin, evaluate the first-party option before this wrapper.
- How should I evaluate or test RunroomUserBundle before adopting it?
- Install it in a throwaway Symfony application and exercise registration, login, password reset, and role escalation end to end. Check whether the split repository is actively synced from the monorepo, where issues and security reports are triaged, and whether Runroom uses it in production today. Ask for a named maintainer contact and confirm the release tags are genuine rather than tooling-generated.