Experience
195 experience to go until the next level!
In case you were wondering, you earn Laracasts experience when you:
- Complete a lesson — 100pts
- Create a forum thread — 50pts
- Reply to a thread — 10pts
- Leave a reply that is liked — 50pts
- Receive a "Best Reply" award — 500pts
Completed
Awards
-
Start Your Engines
Earned once you have completed your first Laracasts lesson.
-
First Thousand
Earned once you have earned your first 1000 experience points.
-
One Year Member
Earned when you have been with Laracasts for 1 year.
-
Two Year Member
Earned when you have been with Laracasts for 2 years.
-
Three Year Member
Earned when you have been with Laracasts for 3 years.
-
Four Year Member
Earned when you have been with Laracasts for 4 years.
-
Five Year Member
Earned when you have been with Laracasts for 5 years.
-
School In Session
Earned when at least one Laracasts series has been fully completed.
-
Welcome To The Community
Earned after your first post on the Laracasts forum.
-
Full Time Learner
Earned once 100 Laracasts lessons have been completed.
-
Pay It Forward
Earned once you receive your first "Best Reply" award on the Laracasts forum.
-
Subscriber
Earned if you are a paying Laracasts subscriber.
-
Lifer
Earned if you have a lifetime subscription to Laracasts.
-
Laracasts Evangelist
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.
-
Chatty Cathy
Earned once you have achieved 500 forum replies.
-
Laracasts Veteran
Earned once your experience points passes 100,000.
-
Ten Thousand Strong
Earned once your experience points hits 10,000.
-
Laracasts Master
Earned once 1000 Laracasts lessons have been completed.
-
Laracasts Tutor
Earned once your "Best Reply" award count is 100 or more.
-
Laracasts Sensei
Earned once your experience points passes 1 million.
-
Top 50
Earned once your experience points ranks in the top 50 of all Laracasts users.
-
Community Pillar
Earned once your experience points ranks in the top 10 of all Laracasts users.
Awarded Best Reply on Connect Laravel To Remote Database Got Connection Timed Out Error
If you're able to connect to the remote server using PHP outside of Laravel, then I suspect this is an issue of your .env file on the server.
Laravel is likely attempting to a hostname that is not accepting connections due to incorrect DB_HOST or similar settings.
A timeout generally means a firewall is blocking you, or the address being connected to cannot be reached, so I suspect the hostname that Laravel is using is (was?) incorrect.
Replied to Connect Laravel To Remote Database Got Connection Timed Out Error
If you're able to connect to the remote server using PHP outside of Laravel, then I suspect this is an issue of your .env file on the server.
Laravel is likely attempting to a hostname that is not accepting connections due to incorrect DB_HOST or similar settings.
A timeout generally means a firewall is blocking you, or the address being connected to cannot be reached, so I suspect the hostname that Laravel is using is (was?) incorrect.
Replied to Looking For Laravel CI/CD Premium Tutorials On Aws K8s Or Ecs
Hi! The Shipping Docker course has a (large!) module on ECS. It uses CodeBuild for CI/CD but that could easily be transferred to GitHub actions, as it just runs some tests and then makes some API calls to AWS to trigger a deployment in ECS.
It gets into some of the details like how to pull in a production .env file in CI/CD when building a Docker image for production, etc.
Replied to Can I Put The Jobs On Different Server? Is This A Bad Approach?
Yep, that's very standard! The thing to worry about, as you mentioned, is your "state" - centralized data storage is needed with multiple servers.
This means each server needs to talk to the same database, same cache, same file storage (e.g. S3, if you use it and if files matter to your queue jobs). 👍
Replied to Cron Job Not Executing Queries On Cpanel (could Not Find Driver)
It sounds like the CRON task is running a different PHP than your web server, or is not using the same php.ini settings.
You might be running php artisan schedule:run but perhaps you need to try php-cli artisan schedule:run or even a specific version of PHP (which would have a different path like /path/to/specific/php).
If you have a custom/different php.ini file that loads in additional php modules, you may need to run a CRON command that uses it, such as: php -v /path/to/custom/php.ini artisan schedule:run.
It will depend on how PHP is setup in your cPanel server. You may want to contact your hosting with this question as how to resolve it will depend on specifics of the server.