Weave Code
Credential Bundle Laravel Package
2lenet/credential-bundle
CredentialBundle is a Symfony bundle offering an easy credential manager for complex applications, simplifying the association between user groups and roles. It ships with French, English and German translations, remote repository integration, and installs quickly via Composer.
The 2LE's Credential Bundle.
Frequently asked questions about Credential Bundle
- Can I use 2lenet/credential-bundle in a Laravel application?
- It is a Symfony bundle rather than a native Laravel package, so Laravel integration requires adaptation. You can attempt it with a Doctrine bridge and replacements for Symfony-specific components. The package shows active Symfony maintenance through PHPStan and PHPUnit badges, but it does not ship Laravel support. Evaluate the integration risk carefully before using it in production.
- How do I install 2lenet/credential-bundle with Composer?
- Install it with composer require 2lenet/credential-bundle. In Symfony, you then configure config/routes/credential.yaml, generate a migration with make:migration, and run doctrine:migrations:migrate. In Laravel, you would need to adapt routing and migrations to Laravel conventions instead of using the Symfony setup steps directly.
- Does 2lenet/credential-bundle support Laravel 9 or Laravel 10?
- There is no official Laravel 9 or Laravel 10 support because the bundle is built for Symfony. You can attempt compatibility with a Doctrine bridge and by replacing Symfony-specific routing, templating, and security pieces. Recent Symfony 8 updates suggest the bundle is maintained for Symfony, not Laravel. Test any Laravel integration thoroughly because it is not a drop-in solution.
- What ORM does 2lenet/credential-bundle use, and can I use Eloquent?
- CredentialBundle relies on Doctrine ORM for its credential, group, and role data. Laravel’s default Eloquent ORM is incompatible, so you would need laravel-doctrine/orm or a hybrid approach. A hybrid model using Doctrine for migrations and Eloquent for queries can work but risks model divergence. Use strict testing if you mix ORMs.
- How does the group-role-permission RBAC model work in CredentialBundle?
- The bundle provides a pre-built RBAC system with group-role-permission matrices. It simplifies associating user groups and roles for complex applications. It includes a dashboard UI, routes integration, Doctrine migrations, and CLI commands. Its Symfony origins suggest robust permission inheritance and conflict resolution.
- What CLI commands are available in 2lenet/credential-bundle?
- The bundle includes warmup, load, and init commands. Warmup automates CRUD permission generation, while load and init help with environment parity such as staging or production seeding. In Laravel, you would need to wrap these commands in Artisan or rebuild them natively. Plan how they integrate with Laravel’s seeder system.
- How do I configure routes and the dashboard UI for CredentialBundle in Laravel?
- Symfony uses YAML routes such as credential.yaml and Twig templates for the dashboard. Laravel requires converting those routes to routes/web.php and replacing Twig with Blade templates. You should also plan authentication and middleware integration for the dashboard. These changes are manual and not provided by the bundle.
- Can I use CredentialBundle's remote repository integration with Laravel Sanctum or Passport?
- The remote repository pattern enables centralized credential management across services or environments. You can expose the required API with Laravel Sanctum or Passport, but the bundle expects a custom endpoint. Handle network failures and offline scenarios because load and init commands may break permission syncs. It may also conflict with existing permission services such as Spatie’s Laravel-Permission.
- What are the alternatives to 2lenet/credential-bundle for Laravel RBAC?
- Spatie laravel-permission is a native Eloquent RBAC package commonly used in Laravel. CredentialBundle is a drop-in solution for Symfony-first applications, not Laravel. For Laravel, compare the overhead of a Doctrine bridge and Symfony component replacements against native packages. Choose based on whether you need the bundle’s dashboard, CLI workflows, and remote repository pattern.
- How should I test and cache permissions when integrating CredentialBundle with Laravel?
- Test Doctrine-Laravel interactions such as migrations and queries, and define a rollback plan for warmup or load commands. Cache permission checks to avoid repeated database or remote API calls. The bundle’s cache invalidation after warmup may conflict with Laravel’s cache drivers. Design invalidation and offline handling carefully for production.
Weaver
How can I help you explore Laravel packages today?