Nick Retel
Nick Retel
To add to this remark: https://github.com/laravel/horizon/issues/1450#issuecomment-2132934935 this only seems to be true in the case of 1 job being processed on termination. When it doesn't occur, the worker is included...
Yeah that makes sense. Would make it more solid/useful as well when explicitly checking for running processes elsewhere in the code. Instead of having to keep adding an extra check...
No worries man, at least its added properly now :) Thanks for looking into it.
Hey Jay as I played this feature a bit already I was wondering what it would look like when running multiple applications on the same server. As you won't deploy...
Been doing some testing, and got it working with multiple swarm stacks. 1 stack for traefik, 1 for redis, and 1 with a laravel project. What's cool about the setup...
You can ignore my remarks, they don't really apply to the issue/feature in question. I'll create a separate feature request.
Looks complete to me. Still need to verify assumptions as discussed on Discord. Will give it this weekend a try.
Alright, I did a test and can confirm everything is working as expected with setting the horizon docker service order to `start-first` in docker-compose, but there are a few more...