Member Since 5 Years Ago
1,895 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.
Earned once your experience points ranks in the top 10 of all Laracasts users.
There are some reasons why we don't do this, but it is definitely another viable option. I actually just set up the laravel-mix env extension and it's working perfectly. A few lines of code and you get to choose which env to set for which build type.
I'm having the same issue and was wondering what the "official" solution to this is. I think one way to handle it would be to have separate .env files for dev and production, and then use a package like the following to switch between them based on what you're building for.
The other option is to just use your production endpoint for Pusher, but prefix all channels with "local-" if you're running on local development. This would ensure that your local testing won't interact inadvertently with any of your live channels. Since Pusher bills you based on your account and not per app, it really doesn't matter if you use production or dev environments for testing.
Replied to Handle HEIC Images
I have the same issue. Imagick works fine with JPEG, PNG, etc. But HEIC images break it. I think there is a way to install imagick specifically with HEIC support but I don't want to break everything and hate doing full re-installs and messing with .ini files if I don't have to. Anybody have any further insight on this?