- Does aldaflux/standard-user-command-bundle work with Laravel?
- It is a Symfony bundle built for symfony/framework-bundle 7.1 or later, so it does not run natively in Laravel. You would need a Symfony Bridge or custom wrapper and adapt Symfony UserProvider and dependency injection assumptions. For most Laravel apps, native Artisan commands are lower risk.
- How do I install aldaflux/standard-user-command-bundle?
- Install with composer require aldaflux/standard-user-command-bundle in a Symfony project. Then use bin/console to run its suc:user commands. In Laravel there is no php artisan integration out of the box.
- What console commands does this Symfony user bundle provide?
- It provides suc:user:list to list registered users, suc:user:add to create regular or admin accounts, and suc:user:change-password to update an existing user's password. The add command can prompt interactively when arguments are missing. The list command defaults to 50 recent users.
- How can I list more than 50 users with suc:user:list?
- Use the --max-results option, for example suc:user:list --max-results=2000. Without it, the command displays only the 50 most recent users. This is useful for large user tables but watch output size.
- How do I create an admin user with suc:user:add?
- Run suc:user:add and provide username, password, email, and optional full name, or let it prompt for missing values. Add the --admin option to create an administrator account instead of a regular user. Example: suc:user:add username password email --admin.
- Can I change a Laravel user's password with suc:user:change-password?
- Not directly, because the command depends on Symfony's user provider and entity assumptions. You can pass a username or email identifier and an optional new password in Symfony. For Laravel, implement an Artisan command using Hash::make and your Eloquent User model.
- What Laravel versions are supported by aldaflux/standard-user-command-bundle?
- None are officially supported; the package targets Symfony 7.1+ via symfony/framework-bundle. Laravel includes symfony/console, but the bundle's DI, security, and user provider expectations do not match Laravel conventions. Treat Laravel compatibility as a custom integration project.
- Is it safe to use this bundle in production?
- Evaluate carefully: the repository shows low adoption (zero stars and dependents) and possible metadata issues such as a 2026 release date. Production use also introduces Symfony DI and console overhead plus potential command conflicts. Run a proof of concept and keep a Laravel-native fallback.
- How does the bundle map to Laravel's Eloquent User model?
- The bundle assumes Symfony UserInterface and UserProvider structures, while Laravel uses Eloquent and its own auth contracts. You would need adapter classes and likely schema adjustments for fields such as is_active. This is non-trivial and can break Laravel authentication conventions.
- What are Laravel alternatives for CLI user management?
- Build custom Artisan commands for listing users, creating accounts, assigning admin flags, and resetting passwords with Hash::make. Use packages like spatie/laravel-permission for roles and Laravel Nova or Filament for admin UI. These avoid Symfony DI and UserProvider mismatches.