- Is monofony/user a Laravel package?
- No. monofony/user is a Symfony component for Monofony applications and builds on the Sylius user component, so it does not provide Laravel auth, Eloquent models, or Laravel service providers. For Laravel user management, use Laravel Breeze, Jetstream, Fortify, or a Laravel-specific package.
- How do I install monofony/user with Composer?
- Run composer require monofony/user in a Symfony or Monofony project. Then register the package configuration and bundle according to your Monofony version, import the Doctrine mappings, and point your Symfony security provider at the User entity. Because the repository is unknown, check the package's composer.json and Monofony documentation for exact bundle class and config paths.
- Which Laravel versions does monofony/user support?
- None. It targets Symfony and Monofony, not Laravel, so there is no Laravel version compatibility matrix. Check its composer.json for Symfony framework and Sylius user component constraints instead.
- What features does the monofony/user User entity provide?
- It ships a prebuilt User entity with roles and authentication support, plus Doctrine mappings and configuration for quick setup. The blurb also lists registration, password reset, and profile editing as part of Monofony User. The model layer is extensible so you can add custom user types or fields.
- Can I add custom fields to the monofony/user User entity?
- Yes. The package describes an extensible model layer, so you can extend the base User entity, add properties, and update the Doctrine mapping. You will also need to adjust forms, validation, and any Sylius resource configuration that references the user class. Test migrations and security provider changes before deploying.
- How does monofony/user integrate with Symfony Security?
- It integrates through the Sylius user and security components, supplying a User entity that Symfony Security can use as the provider. You configure a firewall, a user provider pointing at the entity, and a password hasher in Symfony security.yaml. Role handling comes from the package's roles support, so access_control rules can use those roles.
- Does monofony/user support both admin and shop customer accounts?
- Yes, it is designed for Monofony's admin and shop contexts. You can use the same User entity with roles to separate administrators from customers, or extend the model for distinct user types. The right approach depends on your firewall and role hierarchy design.
- How do I test login and registration with monofony/user?
- Use Symfony's WebTestCase or KernelBrowser to submit login and registration forms, and create test users through the entity manager or a fixture. Run tests against a dedicated test database with migrations applied, and assert redirects, authentication state, and validation errors. The package does not document a test suite here, so test your app's configured firewall and user provider directly.
- What are alternatives to monofony/user?
- You can use the Sylius user component directly if you want fewer Monofony-specific defaults. Other options include a custom Symfony Security user entity, FOSUserBundle for legacy Symfony projects, or MakerBundle-generated authentication. For Laravel, use Laravel Breeze, Jetstream, Fortify, or another Laravel auth package instead.
- Is monofony/user maintained and production-ready?
- The repository is unknown in this context, so verify release activity, open issues, and Symfony version constraints on Packagist before adopting it. Check that it is compatible with your Monofony and Sylius user component versions and has no unresolved security advisories. Pin a tested version and review migrations, password hashing, and firewall configuration before production use.