Is there a shorthand to schedule commands to be queued?

Artisan::queue('email:send', [
    'user' => 1, '--queue' => 'default'
]);

The '--queue' => 'default'-part in your example doesn't automatically queue the artisan command. This is just an option which is passed to the email:send command. The command would then have to read the option and implement the queue itself (https://laravel.com/docs/master/artisan#defining-input-expectations)

May I ask, what exactly you want to accomplish and why? Why do you want to schedule an artisan command?

Why don't you use Jobs? (It seems you already have experience with jobs)

It does seem somewhat of a pointless use case (which is probably why there is no shorthand)

If you have a command to be scheduled and this command requires multiple steps then the command itself should decide if it shoukd queue or not.

For instance, you could write a command to wish all your users Happy New Year, schedule this command to run at midnight, but then the emailer creates a queued job for each mail to be sent.

@_STEFANZWEIFEL - Hmmm, I don't think that's the case. I think it may just be confusing documentation. Because when I run Artisan::queue('command:name');, I see an instance of Illuminate\Foundation\Console\QueuedCommand pushed onto the queue.

Also, as you can see in the docs the the onQueue and onConnection methods can be chained to the call to Artisan::queue():

Artisan::queue('email:send', [
    'user' => 1, '--queue' => 'default'
])->onConnection('redis')->onQueue('commands');

In my case, I have written a command to export some data to an FTP service. Something like php artisan data:export. I want it to be a command so that I can call it manually from the command line when needed (in the same process, not in the background). However, it will mostly be called on a schedule, and sometimes there are errors with the connection. So I wanted to queue the command so it will be retried if there are errors.

What's the best way to do this? I didn't want to create a Job class whose purpose was to trigger the command with Artisan::call(). Maybe I am not thinking about this correctly.

Why not extract the logic of your export/ftp to it's own class - then just call that from both your artisan command and queued job?

@SNAPEY - In my case, I have written a command to export some data to an FTP service. Something like php artisan data:export. I want it to be a command so that I can call it manually from the command line when needed (in the same process, not in the background). However, it will mostly be called on a schedule, and sometimes there are errors with the connection. So I wanted to queue the command so it will be retried if there are errors.

What's the best way to do this? I didn't want to create a Job class whose purpose was to trigger the command with Artisan::call(). Maybe I am not thinking about this correctly.

@OHFFS - I could, but then I still have a command and a job doing the exact same thing. I was under the impression the command could just be queued, which is why the Artisan::queue() method and the Illuminate\Foundation\Console\QueuedCommand class exist.

your command should queue the job and your scheduler should call the command.

@SNAPEY - Ok, that makes sense, but I am still confused about one thing. If the command queues the job, is there any way for me to run the logic in the Job without hitting the queue. If I want to go to the command line and manually run the command with artisan, how can I set it up so the command doesn't always hit the queue, but instead just runs the code in the current process?

Should I add a 'queue' option to the command, and maybe have the default set to 'sync', so it runs immediately if no queue is specified?