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
Any ideas/suggestions on how to handle a queue worker? I assume the easiest would be to use supervisor and add another config setting similar to how the horizon is handled.
But I think a better solution would be to have a separate container for the queue worker?
Anyone figure that part out?
The text was updated successfully, but these errors were encountered:
I guess the only benefits of having it separate is running more than a single queue worker, or doing more advanced stuff such as queue specific memory/cpu restrictions or what not.
From a docker point of few, having the site and queue in the same container seems wrong from a separation point of view.
Yeah thats the way I would do it, though I've only ever worked with queues via horizon. Is there a reason why you're not using it?
I was not aware that horizon command ran anything but the horizon interface, I didn't know it ran a queue worker as well.
Hello,
Any ideas/suggestions on how to handle a queue worker? I assume the easiest would be to use supervisor and add another config setting similar to how the horizon is handled.
But I think a better solution would be to have a separate container for the queue worker?
Anyone figure that part out?
The text was updated successfully, but these errors were encountered: