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
{{ message }}
This repository was archived by the owner on Nov 5, 2025. It is now read-only.
Copy file name to clipboardExpand all lines: readme.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,6 +3,7 @@
3
3
4
4
Just like the 'sync' driver, this is not a real queue driver. It is always fired immediatly.
5
5
The only difference is that the closure is sent to the background without waiting for the response.
6
+
This package is more usable as an alternative for running incidental tasks in the background, without setting up a 'real' queue driver.
6
7
7
8
> **Note:** If you are coming from 0.1.0 (or dev-master), you will need to run the migrations, since the new versions uses a database to store the queue.
8
9
> If you are on Laravel 4.0 or 4.1, you can still require 0.1.x for the old way.
@@ -33,6 +34,6 @@ You should now be able to use the async driver in config/queue.php
33
34
}
34
35
35
36
It should work the same as the sync driver, so no need to run a queue listener. Downside is that you cannot actually queue or plan things.
36
-
Queue::later() is also fired directly.
37
+
Queue::later() is also fired directly, but just runs `sleep($delay)` in background..
0 commit comments