tylernathanreed

tylernathanreed

Member Since 4 Years Ago

Dallas

Experience Points
53,710
Total
Experience

1,290 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
648
Lessons
Completed
Best Reply Awards
13
Best Reply
Awards
  • start-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-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-token Created with Sketch.

    Subscriber

    Earned if you are a paying Laracasts subscriber.

  • lifer-token Created with Sketch.

    Lifer

    Earned if you have a lifetime subscription to Laracasts.

  • lara-evanghelist 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 11
53,710 XP
Sep
22
3 months ago
Activity icon

Replied to Make A Job Wait On Several Other Jobs

@bobbybouwmann

I'm not certain your first solution would work. Let's say the "A-finished" job gets dispatched, and then "B", "B", and "B-finished" are dispatched concurrently. If I had three queue listeners, then all three jobs would get picked up. This would cause "B-finished" to run early.

For you alternative solution, what would trigger the cronjob? My goal here is to essentially have both multi-threading (by running jobs in parallel) and process-dependency (by using chaining or some other approach).

My application currently has 7 processes that need to be chained, and each process currently runs actions in a loop over a series of models. However, each model-specific action is isolated to that model, so I'd like to run that part concurrently.

Here's the sort of workflow I'm expecting:

  1. Dispatch the first process ("A")
  2. "A" dispatches 5+ "A-record" processes
  3. Something ("A", "A-record", or other) dispatches the second process ("B") when all "A-record" processes are complete
  4. "B" dispatches 300+ "B-record" processes
  5. Something dispatches the third process ("C"), similar to #3
  6. "C" dispatches 8000+ "C-record" processes
  7. etc.

Since my plan here is to use Laravel Vapor in the long run, when something like #6 happens, I'm expecting 8000+ queue listeners to spin up, handle the job, and spin down. I'm currently just operating in a basic Laravel environment, so I'll likely only have 1 to 4 listeners always running until I get this process ironed out. If I were to chain the 8000 job instances together, then they'd run sequentially, rather than in parallel.

I think my biggest problem here is knowing when to dispatch the next process that has a dependency (i.e. #3 and #5). I can envision various ways of tackling this problem, but they all of pros and cons that make me worry that I'm not thinking about the solution in the correct manner (hence why I'm coming here for insight).

Sep
19
4 months ago
Activity icon

Started a new Conversation Make A Job Wait On Several Other Jobs

Is there a "best practice" for having a job in Laravel wait on several other jobs? I'm aware of the "job chaining" functionality in Laravel, but it doesn't do quite what I want.

For example, I have a job ("A") that dispatches multiple jobs ("B"), and another job ("C") chained to the first job ("A"). If I had to put this in a topological order, it would look like this:

"A" > "B", "B", "B", "B" > "C"

Where the first job "A" runs, dispatches all of the "B" jobs (which can run in parallel), but "C" can't run until all instances of "B" are cleared from the queue.

What is the best way to achieve this functionality?

I hoping to move my current application into Laravel Vapor once I have my queuing process ironed out, so I'd like the solution for this to work in an auto-scaling environment.

Jul
25
5 months ago
Activity icon

Replied to Custom LoginController For Nova

@mrwilde @martinfolkerts

I know this is old, but I just found a solution that works better for me.

In the Nova Service Provider, you can alias Nova's Login Controller for your own, meaning when the routing layer creates the Login Controller, it's using yours instead of Nova's.

Example:

    /**
     * Bootstrap any application services.
     *
     * @return void
     */
    public function boot()
    {
        parent::boot();

        $this->app->alias(
            \App\Http\Controllers\Nova\LoginController::class,
            \Laravel\Nova\Http\Controllers\LoginController::class
        );
    }