-
Notifications
You must be signed in to change notification settings - Fork 41
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
Queue? #6
Comments
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?
At first glance I can't see any benefits to having it separately, seems to unnecessarily complicate things. Am I missing something? |
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.
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: