The default queue "driver" is actually a "connection"
The description here has bothered me for a while, because it is kind of misleading. The `QUEUE_DRIVER` environment variable perhaps also needs changing to `QUEUE_CONNECTION`, but I'm not sure if that is just too engrained in legacy systems now? I can change that on this PR if you agree, and also the matching `QUEUE_DRIVER=sync` in `.env.example`.
This commit is contained in:
parent
c892bd367c
commit
37b9e0f76d
|
@ -4,12 +4,12 @@
|
||||||
|
|
||||||
/*
|
/*
|
||||||
|--------------------------------------------------------------------------
|
|--------------------------------------------------------------------------
|
||||||
| Default Queue Driver
|
| Default Queue Connection
|
||||||
|--------------------------------------------------------------------------
|
|--------------------------------------------------------------------------
|
||||||
|
|
|
|
||||||
| Laravel's queue API supports an assortment of back-ends via a single
|
| Laravel's queue API supports an assortment of back-ends via a single
|
||||||
| API, giving you convenient access to each back-end using the same
|
| API, giving you convenient access to each back-end using the same
|
||||||
| syntax for each one. Here you may set the default queue driver.
|
| syntax for each one. Here you may set the default queue connection.
|
||||||
|
|
|
|
||||||
| Supported: "sync", "database", "beanstalkd", "sqs", "redis", "null"
|
| Supported: "sync", "database", "beanstalkd", "sqs", "redis", "null"
|
||||||
|
|
|
|
||||||
|
|
Loading…
Reference in New Issue