4,635 experience to go until the next level!
In case you were wondering, you earn Laracasts experience when you:
Earned once you have completed your first Laracasts lesson.
Earned once you have earned your first 1000 experience points.
Earned when you have been with Laracasts for 1 year.
Earned when you have been with Laracasts for 2 years.
Earned when you have been with Laracasts for 3 years.
Earned when you have been with Laracasts for 4 years.
Earned when you have been with Laracasts for 5 years.
Earned when at least one Laracasts series has been fully completed.
Earned after your first post on the Laracasts forum.
Earned once 100 Laracasts lessons have been completed.
Earned once you receive your first "Best Reply" award on the Laracasts forum.
Earned if you are a paying Laracasts subscriber.
Earned if you have a lifetime subscription to Laracasts.
Earned if you share a link to Laracasts on social media. Please email [email protected] with your username and post URL to be awarded this badge.
Earned once you have achieved 500 forum replies.
Earned once your experience points passes 100,000.
Earned once your experience points hits 10,000.
Earned once 1000 Laracasts lessons have been completed.
Earned once your "Best Reply" award count is 100 or more.
Earned once your experience points passes 1 million.
Earned once your experience points ranks in the top 50 of all Laracasts users.
Replied to Multiple Auth Guards Vs Roles / Permissions
Thanks Bobby, I think this is what I needed to hear
Started a new Conversation Multiple Auth Guards Vs Roles / Permissions
So I am in the process of building a new app, and I am stuck on what would be considered the best approach to handle authentication.
The app in question needs to allow the following :-
Regular user registration (automatic email confirmation, and then log in once email has been verified)
Regular user login through
Vendor registration (this won't allow the user to login until they have been approved as a vendor, so the flow is different to regular users)
Vendor login through
Admin user login, this is basically the owner of the site, and they will be able to approve or deny vendor registrations.
In my head I am thinking I would use three different auth guards, and a table for each type of user, however I keep wondering if the better approach here would be to use a single users table, a single auth guard but the use something like a permissions / roles system to differentiate between the user types.
The only reason I am thinking a role base system wouldn't work so well is because vendors and users will have a totally different registration flow and need to login via different URLs.
Has anyone any thoughts on this type of multi user table approach, I can't work out if I like the approach or not, or if there is a more structured way.
Commented on Roles And Abilities
I always prefer to "roll" my own system like this, third party packages tend to carry way more than I ever need and this approach keeps it simple.