You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+9-1Lines changed: 9 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -52,7 +52,7 @@ php artisan operations:process // process all new operation fi
52
52
php artisan operations:process --sync // force syncronously execution
53
53
php artisan operations:process --async // force asyncronously execution
54
54
php artisan operations:process --test // dont flag operations as processed
55
-
php artisan operations:process --isolated // Do not run the commandif another instance of the command is already running
55
+
php artisan operations:process --isolated // run commandisolated
56
56
57
57
php artisan operations:process --queue=<name> // force queue, that the job will be dispatched to
58
58
php artisan operations:process --tag=<tagname> // only process operations, that have the given tag
@@ -228,6 +228,14 @@ You can provide the `--queue` option in the artisan call. The given queue will b
228
228
php artisan operations:process --queue=redis // force redis queue
229
229
```
230
230
231
+
### Run commands isolated on Multi-Server Architecture
232
+
233
+
If you work with a Multi-Server Architecture you can use `--isolated` option to make sure to only run one instance of the command ([Laravel Isolatable Commands](https://laravel.com/docs/10.x/artisan#isolatable-commands)).
234
+
235
+
```shell
236
+
php artisan operations:process --isolated
237
+
```
238
+
231
239
### Run only operations with a given tag
232
240
233
241
You can provide the `$tag` attribute in your operation file:
0 commit comments