Replies: 2 comments
-
|
Hm. Interesting scenario... But i didn't see a easy way to do this, sorry. Maybe it's possible to reduce the worker by setup a minimal django environment. But i think a "smaller" is not worth the effort. The profit is not big enough. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Thank you for the response! In the end I ended up addressing my problem by just relying more on logging (EFK stack). |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Thanks for the awesome project! I have a question that might be out of scope, but I'd appreciate any pointers.
I've been using Huey in a django project without
huey.contrib.djhuey, so that I can run ahuey_consumeron a different machine where the django application is not fully set up (the code is obviously accessible). I've organized my code as described here and on the other machine, I start a worker like this:REDIS_HOST=172.0.20.2 huey_consumer app.huey.main.huey. This works great and makes it so that I don't have to install anything on the worker node other than huey and redis-py.However, I can't figure out a way to wire up huey-monitor to all of this. Is there a mechanism by which I can provide it with a huey instance?
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions