Level 21
@Swaz Its like for queues to take effect. You need to run the queue:listen and yes for every restart of server you have to run it. You can automate it by setting the cron job or by adding it to deploy script.
Apr 17, 2015
3
Level 20
Queue Worker
I have beanstalkd installed and have been using Mail::queue() to send emails. I used forge to start Queue Worker on the server. This was working great until I switch to Envoyer. Now it seems I have to run php artisan queue:listen on the server to start the queue worker. So forge must of done that automatically? Do I run queue:listen on every deploy, or do I just have to do it once every time I restart the server? If so, is there a way to automate it?
Level 20
It looks like forge DOES automatically run queue:listen on server start and watches it with supervisor. I don't know why it wasn't working last night but everything is fine today. I must have forgot to click my heals twice.
Level 9
@Swaz Out of curiosity, what type of errors did it throw, if any? I've been unable to get Beanstalkd to work on a Digital Ocean droplet created by Forge, running Laravel 5. I can't remember if the issue began before or after I started using Envoyer.
Does Envoyer actually restart the server on every deployment?
1 like
Please or to participate in this conversation.