#celery

acmehandle: depends on how you run celery

the workers

Ok, I had thought that with the newer version of Celery since it has done away with the django-celery app that those supervisor config files may not be relevant to the new version of celery.

when you run celery that's a process, supervisor is a process manager

it makes sure that when your process dies it gets restarted

so these config files are always relevent no matter what version of celery you have installed

I should clarify what I meant. What I meant to say was if these particular config files were outdated and that there may have been an updated version of them. But that doesnt seem to be the case then.

But I understand. Thank you

Looks like Celery beat is just a task schedulre

scheduler.

A cron job manager of sorts.

The better answer would have been to say that the celery_beat is the task scheduler. How I run celery is not really relevant because celery however it runs. The worker is designed to run as a task manager for a process or program that I decorate. Whereas it appears celery beat is designed to run schedule tasks

I hope you dont get paid to do this.

With the setup_logging signal how I can I provide additional arguments of my own? It doesn't seem to trigger if I use anything like a partial

acmehandle: you didn't ask about celery beat

hello all, i've got this PR waiting for comments : https://github.com/celery/py-amqp/pull/59

travis failed but i don't know why

(looks like the travis file is missing :/)

it fixes an issue that makes celery crashes when an ssl connection is remotely hang up (im some cases)

geekou: thanks, I'll be able to look at this soon

hi, anyone able to give me a hand on kombu?