JussiMannisto

JussiMannisto

Member Since 2 Years Ago

Experience Points
600
Total
Experience

4,400 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
Lessons Completed
0
Lessons
Completed
Best Reply Awards
0
Best Reply
Awards
  • start your engines Created with Sketch.

    Start Your Engines

    Earned once you have completed your first Laracasts lesson.

  • first-thousand Created with Sketch.

    First Thousand

    Earned once you have earned your first 1000 experience points.

  • 1-year Created with Sketch.

    One Year Member

    Earned when you have been with Laracasts for 1 year.

  • 2-years Created with Sketch.

    Two Year Member

    Earned when you have been with Laracasts for 2 years.

  • 3-years Created with Sketch.

    Three Year Member

    Earned when you have been with Laracasts for 3 years.

  • 4-years Created with Sketch.

    Four Year Member

    Earned when you have been with Laracasts for 4 years.

  • 5-years Created with Sketch.

    Five Year Member

    Earned when you have been with Laracasts for 5 years.

  • school-in-session Created with Sketch.

    School In Session

    Earned when at least one Laracasts series has been fully completed.

  • welcome-newcomer Created with Sketch.

    Welcome To The Community

    Earned after your first post on the Laracasts forum.

  • full-time-student Created with Sketch.

    Full Time Learner

    Earned once 100 Laracasts lessons have been completed.

  • pay-it-forward Created with Sketch.

    Pay It Forward

    Earned once you receive your first "Best Reply" award on the Laracasts forum.

  • subscriber Created with Sketch.

    Subscriber

    Earned if you are a paying Laracasts subscriber.

  • lifer Created with Sketch.

    Lifer

    Earned if you have a lifetime subscription to Laracasts.

  • evangelist Created with Sketch.

    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 Created with Sketch.

    Chatty Cathy

    Earned once you have achieved 500 forum replies.

  • lara-veteran Created with Sketch.

    Laracasts Veteran

    Earned once your experience points passes 100,000.

  • 10k-strong Created with Sketch.

    Ten Thousand Strong

    Earned once your experience points hits 10,000.

  • lara-master Created with Sketch.

    Laracasts Master

    Earned once 1000 Laracasts lessons have been completed.

  • laracasts-tutor Created with Sketch.

    Laracasts Tutor

    Earned once your "Best Reply" award count is 100 or more.

  • laracasts-sensei Created with Sketch.

    Laracasts Sensei

    Earned once your experience points passes 1 million.

  • top-50 Created with Sketch.

    Top 50

    Earned once your experience points ranks in the top 50 of all Laracasts users.

Level 1
600 XP
Oct
17
1 week ago
Activity icon

Replied to Prevent Overlapping Of Two Different Commands

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.

Activity icon

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.

Oct
02
3 weeks ago
Activity icon

Replied to Framework Dependency In Composer.json For Laravel/Lumen Packages

Thank you. I guess I have to go through my packages and see what parts they need.

Activity icon

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.