I am considering using symfony2 over flat php for my next project. I am, however, a little bit worried about a few things. One of them is whether this will be a great challenge for me to learn:
I have to set up a system where I access a backend part to create user-accounts.
Each customer has a user account that will work like their admin. Then, within their control panel, they can create users within their company, and set login and password for them. I won't, of course, restrict each company to only use usernames that no one else has used, so there must be one selector for the company and one for the username on the main login screen, alt. They will log in on a route, say site.com/company/.
I have no idea where to start or how complicate this will be to create. I have tested symfony2 around a little bit and for the main part (DB and templating) it seems just what I need.
Would one approach perhaps be to use usergroups, and set up the grouops=companies from my backend part, and let the companies add users to their group only?
There will also be access rights etc. In flat PHP I just control it through an access table user-contentpiece but perhaps symfony offers a smoother way...
Any enlightening comments for me? Is fosUserBundle a good option or should I build from scratch?
I suppose that it isn't a symfony2 problematique or FOSUserBundle one.
You can take advantage of FOSUserBundle features and make some extra controls (by overwriting or extending existing methods) like i.e. before update or delete a user, is that authenticated user into same company of user that will be updated/deleted?
Moreover you can modify FOSUserBundle's User entity by adding an extra field that will be an external key with company id and make this plus user id new primary key for User entity.
So, if you can "study" a little bit of Symfony and FOSUserBundle, that's absolutely a good choice but build it from scratch (if you only need THAT functionlaity) is as much a good choice and exercise