Member Since 2 Years Ago
4,400 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.
That's just dodging the question. Also, the sequence doesn't matter. What matters is that they don't run concurrently. It's easy to do in many ways, but I'd like to learn if there's a built-in way through the scheduler.
Looks like the way to do it is through a custom Mutex implementation set via
Event::preventOverlapsUsing(Mutex). Simply scheduling one event and passing its mutex object to the other event doesn't work; the other event will never get executed.
Started a new Conversation Prevent Overlapping Of Two Different Commands
I have a scheduled maintenance command A and a scheduled updater command B. I'd like to prevent these commands from running concurrently.
Event::withoutOverlapping() only prevents a command overlapping with itself, so it won't help.
Does Laravel have an inbuilt mechanism for this, like sharing the mutex between two commands?
Ps. I know there are many ways of doing this, like file locks etc., but I'm interested if Laravel has something to offer.
Thank you. I guess I have to go through my packages and see what parts they need.
Started a new Conversation Framework Dependency In Composer.json For Laravel/Lumen Packages
I've developed several packages that work with both Laravel and Lumen. They use many of Laravel's features; eloquent, facades, localization, artisan etc.
What is the convention in defining the framework dependency (Laravel OR Lumen) in composer.json? Right now I've just left it out and mentioned it in the description.