2,535 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.
Commented on Handling Unique Slugs In Laravel
For anyone watching this for a newer Laravel version. Pluck now returns a collection. So you have to change the if check to :
Using the build-in api resources is a must, the provided articles are dated in that regard https://laravel.com/docs/6.x/eloquent-resources
Replied to Create Or Attach
Use sync() or attach() / detach() https://laravel.com/docs/5.8/eloquent-relationships#updating-many-to-many-relationships
Next time use google or the documentation :) they both are pretty good.
Not really sure what the adding-customer-user-providers does not explain? The point of your custom provider is that it has custom code related to your use-case?
And a user-provider alone is probably not enough so also take a look at the custom guards: https://laravel.com/docs/5.8/authentication#adding-custom-guards
But when reading your post I think you actually just want to authenticate with an existing forum user, in that case, you probably want to use this: https://laravel.com/docs/5.8/socialite Take a look at the custom driver website https://socialiteproviders.netlify.com/, you can create your own custom driver for IP-board
IPBoard as a single-sign-on method which is probably what you need. Read the documentation and add your own socialite driver.https://invisioncommunity.com/services/sso/
Replied to Polymorphism
If you are sure posts/groups are always exactly the same then sure you can use polymorphism, but if there differences between the two or you expect more differences in the future, you should just make 2 tables: Groups/posts. And yes they will both have similar columns, but that doesn't matter and will be way easier to manage in your code.
Replied to Polymorphism
I don't really see the need for multiple tables. You can have a simple type column or just a bunch of date/boolean columns like: favorited_at or is_spam. In your code you can setup Scopes to simplify retrieving the results