@@ -73,7 +73,7 @@ Add connection to `config/queue.php`:
73
73
### Optional Config
74
74
75
75
Optionally add queue options to the config of a connection.
76
- Every queue created for this connection, get's the properties.
76
+ Every queue created for this connection, gets the properties.
77
77
78
78
When you want to prioritize messages when they were delayed, then this is possible by adding extra options.
79
79
@@ -100,13 +100,13 @@ When you want to prioritize messages when they were delayed, then this is possib
100
100
],
101
101
```
102
102
103
- When you want to publish messages against an exchange with routing-key's , then this is possible by adding extra options.
103
+ When you want to publish messages against an exchange with routing-keys , then this is possible by adding extra options.
104
104
105
105
- When the exchange is omitted, RabbitMQ will use the ` amq.direct ` exchange for the routing-key
106
106
- When routing-key is omitted the routing-key by default is the ` queue ` name.
107
107
- When using ` %s ` in the routing-key the queue_name will be substituted.
108
108
109
- > Note: when using exchange with routing-key, u probably create your queues with bindings yourself.
109
+ > Note: when using an exchange with routing-key, you probably create your queues with bindings yourself.
110
110
111
111
``` php
112
112
'connections' => [
@@ -139,7 +139,7 @@ by adding extra options.
139
139
- When routing-key is omitted, the routing-key by default the ` queue ` name is substituted with ` '.failed' ` .
140
140
- When using ` %s ` in the routing-key the queue_name will be substituted.
141
141
142
- > Note: When using failed_job exchange with routing-key, u probably need to create your exchange/queue with bindings
142
+ > Note: When using failed_job exchange with routing-key, you probably need to create your exchange/queue with bindings
143
143
> yourself.
144
144
145
145
``` php
@@ -171,7 +171,7 @@ Those messages probably won't respect Laravel's job payload schema.
171
171
The problem with these messages is that, Laravel workers won't be able to determine the actual job or class to execute.
172
172
173
173
You can extend the build-in ` RabbitMQJob::class ` and within the queue connection config, you can define your own class.
174
- When you specify an ` job ` key in the config, with your own class name, every message retrieved from the broker will get
174
+ When you specify a ` job ` key in the config, with your own class name, every message retrieved from the broker will get
175
175
wrapped by your own class.
176
176
177
177
An example for the config:
@@ -256,8 +256,8 @@ class RabbitMQJob extends BaseJob
256
256
257
257
## Laravel Usage
258
258
259
- Once you completed the configuration you can use Laravel Queue API. If you used other queue drivers you do not need to
260
- change anything else. If you do not know how to use Queue API, please refer to the official Laravel
259
+ Once you completed the configuration you can use the Laravel Queue API. If you used other queue drivers you do not need to
260
+ change anything else. If you do not know how to use the Queue API, please refer to the official Laravel
261
261
documentation: http://laravel.com/docs/queues
262
262
263
263
## Laravel Horizon Usage
0 commit comments