Member Since 3 Years Ago
280 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 Migrating An Old Project To Latest
@martinbean @talinon : I am going to maintain two codebases becasue the current codebase is a live project, developed overa couple of years. And there are new features needing to be introduced constantly. So it is not possible to stop new development. At the same time i do not want to keep developing on old version of laravel. So my plan is to introduce new features that have almost no dependency on the old codebase models/logics etc. I can develop those features in a new version of laravel, but the users should not have to visit a new url or subdomain. Rather I want the request s to land on the current project and if the url relates to the new feature on the new codebase, it should be served from there.
I got suggestion of using PHP Guzzle http client package. That is one option. I was looking for more interesting ideas.
Started a new Conversation Migrating An Old Project To Latest
I am planning to migrate a laravel project built with laravel 5.2. I have a list of new features that i want to add to my project, but i want to develop these in laravel 7. That means I have two codebases for the same application(logically). Over time i will phase out the old codebase as i migrate/develop old/new features in the new codebase.
Looking for suggestions on how to achieve this.
etc. etc. Please put your valuable thoughts in the comments.
Started a new Conversation Limitation Of Laravel Migration Tool
I am relatively new to laravel in a sense that all I have is personal project experience. Been into web dev for about 2.5 years and was trying to get into a job that had laravel stack. So recently on an interview I was asked whether I know about any limitations of the laravel migration tool? I din't. There must be, everything has pros/cons. So, what are the top few limitations of laravel migration tool?