[8.x] Adds "schedule:work" command

[hivokas]

Right now there are 2 options to test the scheduler:

• run schedule:run by hand every minute (that's annoying);
• add the Cron entry to the system (you probably don't want to do that just to test the things).

This new schedule:work command emulates the second option by running schedule:run command every minute under the hood.
When you want to stop the worker, just use Ctrl+C.

Inspired by laravel/ideas#2338

[driesvints]

The scheduler was meant to be used in combination with a daemon that runs it every minute and obviously not manually by hand 😅

[hivokas]

The scheduler was meant to be used in combination with a daemon that runs it every minute and obviously not manually by hand 😅

Yeah, I know 😅 But I'm talking about the cases when you just want to test something & don't want to add the Cron entry to the system for this testing.

[driesvints]

Ah I see. Hmm yeah could be cool actually! Wondering if we can't just add a --daemon flag to the schedule:run command instead of a new command?

[hivokas]

Wondering if we can't just add a --daemon flag to the schedule:run command instead of a new command?

Let's see what others think. I'd rather leave a schedule worker as a separate command to avoid the complexity of schedule:run command.

[taylorotwell]

Don't you need to register the command with the framework?

[hivokas]

Don't you need to register the command with the framework?

Oh, I forgot about that because Laravel automatically detects commands inside the application 😅
I'll register it and update the PR shortly.

[hivokas]

@taylorotwell I've updated the PR

[ottoszika]

I think this feature should be just for local development and not for production. It could behave differently than traditional Unix cron jobs.
Just an example:

• Job A, running at 08:00 PM
• Job B, running at 08:05 PM

If Job A is a long-running one with a 10m duration, we just lose the due time of the Job B, and it won't be handled.
In other words: jobs will need to wait for each other.

[TitasGailius]

This is hot 🔥. Previously, I was running this command to basically achieve the same thing:

while true; do php artisan schedule:run; sleep 60; done

[hivokas]

@ottoszika check it out #34736

[kheme]

Will this also be coming to Lumen?

[samuelcecilio]

@hivokas can i use this in production?

// start.sh

composer dump-autoload --optimize
php /var/www/artisan optimize
php /var/www/artisan migrate --no-interaction --force
supervisord -c /var/www/supervisord.conf

// supervisord.conf

...

[program:schedule]
command=php /var/www/artisan schedule:work
autorestart=true
stdout_events_enabled=true
stderr_events_enabled=true
stdout_logfile_maxbytes=0
stderr_logfile_maxbytes=0
stdout_logfile=/dev/stdout
stderr_logfile=/dev/stderr
stopwaitsecs=3600