Member Since 4 Years Ago
1,985 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 Pay After Taking A Commission In Paypal?
See paypal adaptive payment or chained payment.
Replied to Relation Not Working
Found this: https://github.com/topclaudy/compoships
Eloquent doesn't support composite keys. As a consequence, there is no way to define a relationship from one model to another by matching more than one column. Trying to use where clauses (like in the example below) won't work when eager loading the relationship because at the time the relationship is processed $this->l2 is null.
That's why we should have unique id for each row :rolleyes:
Replied to Fast Auto-Complete
@diegodss maybe now we can use Laravel Scout instead... (yes, it's still using Algolia anyway)
Replied to Single Code Base - Multiple Projects
I agreed to modular code approach which means you need to split your code in packages like snez1983 said. Laravel (as well as other frameworks) provides a way to do it, please take a look at Service Provider, Service Container and Package Development in the documentation.
As for multi tenancy, I don't think it's about managing our code, instead it's about separating data to keep separate users to have their own "isolated" data.
About using git branches, while it looks possible, things will become cumbersome to maintain as sooner or later there will be lots of difference for each branch. Git is version control so the best way is using git for versioning your packages, not for maintaining the raw code base for several projects.