@@ -49,7 +49,7 @@ php artisan operations:make <operation_name> // create operation file
4949php artisan operations:process // process operation files
5050php artisan operations:process --sync // force syncronously execution
5151php artisan operations:process --async // force asyncronously execution
52- php artisan operations:process --queue=< name> // force queue that the job will be dispatched to
52+ php artisan operations:process --queue=< name> // force queue, that the job will be dispatched to
5353php artisan operations:process --test // dont flag operations as processed
5454php artisan operations:process < operation_name> // re-run one specific operation
5555```
@@ -166,7 +166,7 @@ By default, the operation is being dispatched to the `default` queue of your pro
166166You can also execute the code syncronously by setting the ` $async ` flag to ` false ` .
167167_ (this is only recommended for small operations, since the processing of these operations should be part of the deployment process)_
168168
169- ** Hint:** If you use syncronous processing, the ` $queue ` attribute will be ignored.
169+ ** Hint:** If you use syncronous processing, the ` $queue ` attribute will be ignored (duh!) .
170170
171171### Processing the operations
172172
@@ -203,7 +203,7 @@ since an error in your operation could make your whole deployment fail.
203203
204204### Force different queue for all operations
205205
206- You can ignore the ` $ queue` attribute of all operation files by providing the ` -- queue` option in the artisan call:
206+ You can provide the ` -- queue` option in the artisan call. The given queue will be used for all operations, ignoring the ` $ queue` attribute in the class.
207207
208208``` shell
209209php artisan operations:process --queue=redis // force redis queue
0 commit comments