Uninstalling FOSUserBundle and Living Happily
summary
Argues for removing FOSUserBundle and instead implementing a custom user domain using a User entity plus repository, Symfony Security component, Doctrine, and custom forms and templates. Points out problems with FOSUserBundle such as forced username and salt, roles stored as serialized array, restrictive default password limits, and unnecessary translations; shows that rebuilding controllers and functional tests yields a leaner solution without superfluous fields and behaviors.
AI-written summary · about
chapters (5)
- 0:00Introduction
- 4:24FOSUserBundle overview
- 10:55FOSUserBundle problems
- 15:12Replacing FOSUserBundle
- 20:15Q&A
related talks
39mSymfony without the framework bundle
34mDon't Let the Framework Stand in Your Way
56mThe absolute beginner's guide to Domain Driven Design with Symfony
41mMinimal Symfony in real life
02h 09mSymfony Forms in Detail
49mForms in Symfony 3
02h 27mSymfony 4 best practices (Part 1)
37mOverriding Symfony in a million ways