3,540 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 .env Not Reading Variables Sometimes
I face that error, in my case y was running laravel on apache and some queue workers with supervisor. I found that when the .env change I must reload the workers manually with supervisorctl restart all or the changes wont work. If you are using the cli (ie php artisan command) the .env file is only reloaded when you restart the cli process In production before any cli/process restart i use the following command as say in other comments:
php artisan config:cache php artisan config:clear php artisan cache:clear
Replied to Fail Queue In Laravel
you are creating or updating some element in your models inside in your queue work? i think you have a table with an id column that is an uuid; sometimes when a new element is created the new uuid generated exists in the database so the database complain about that when it tries to insert it.