-
Notifications
You must be signed in to change notification settings - Fork 98
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Different sending and listening queues? #13
Comments
You could either create one more connection in config/queue.php using the same driver (sqs-plain) or use Laravel's onQueue() method when you dispatch a job - this will override the queue name (leaving the same AWS customer id/region/etc) |
Thank you! |
Another question for you. I'm using laravel 5.4. When I pasted the code from the readme for receiving messages, it gave me a class not found error for app/Jobs/Job. If I comment out 'extends Job' from my handler, then it runs, but handle() is never called and the message is never pull from the queue. Do I need to define a Job class, and if so, what should it look like? |
I got it working. I ended up just not subclassing job. |
How would I configure laravel-plain-sqs if I want to listen to one particular queue, but send to another?
The text was updated successfully, but these errors were encountered: