Member Since 9 Months Ago
1,070 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.
@martinbean I'm going to give this a go tomorrow, as I have found some stuff online that my help me get this working like you have said.
I can't wrap my head around one thing though. If I had an application that was purely for authenticating users, it would obviously need to have a User model in the project, so that it can store them in the database. Would each application that authenticates against the central application also be required to contain the exact same models (i.e. User). Sorry if it is a stupid question, but just say you have a User has many Posts blog situation, you would need the User model to exist in both right?
Isn't that just for the session. Not like the actual lines in the database and the model etc...
Do you know if there's any documentation surrounding how I would approach this? I can imagine an API with a User model, but then on the actual Laravel projects (not API) how would I have relationships between the API user model and models that are specific to that project.
Started a new Conversation Sharing Users Between Multiple Laravel Projects
Me and a colleague are making a couple of applications that are going to use a Laravel backend API with front-end Vue application. The applications aren't really linked heavily enough to be part of the same project.
We want to share User accounts between the applications, which will probably grow to incorporate new projects in the future. However I am finding a lot of conflicting advice online with how to handle this.
Some people are saying to do it via a composer package (If I am understanding correctly), while we were wondering if we could just have a third Laravel project which just acts an an API which servers the users. Though I am not sure if we would have any issues with the Passport API tokens if taking the second approach.
Are there any standard approaches / supporting documentation for how to accomplish this? Any advice or guidance would be greatly appreciated.