Level 2
Does restarting the queue on deployment not fix the issue regarding queue workers?
Apr 18, 2015
3
Level 3
Using an existing forge site with envoyer
I thought I'd make an FYI post for anyone interested in using an existing forge site with envoyer, without wiping out the site and starting over. Here are the things I've run into so far:
-
Site location needs to be updated in nginx.conf. You'll need to add the /current/ directory anywhere there's a full path to your site. So
/home/forge/example.com/publicbecomes/home/forge/example.com/current/public -
Queue workers started in forge will fail because they are looking for artisan in your original path, not the
/currentpath. You can update these on your server in/etc/supervisor/conf.d/worker-xxxx.conf. Update the path name in the conf file thensudo supervisorctl reloadto apply your changes.
If there are other things you've run into, feel free to add them below
Level 3
No, because it needs to be restarted at the process level, not the application/request level
Level 2
I guess what I'm recalling wondering is are you saying you have to run sudo supervisorctl reload every time you deploy w/ Envoyer or just on the initial setup if you're moving a site deployed from Forge to Envoyer?
Please or to participate in this conversation.