convore.json/groups/django-community/best-practices-for-multi-celeryd-config-1/messages.json

[{"user_id": 3580, "stars": [], "topic_id": 39679, "date_created": 1308346402.523196, "message": "New to celery.. I've been using it in dev but now trying to roll out some server configs. I have multiple django instances on a server, and I want a celeryd instance for each instance. Is there a preferred way to set up these configs? The init.d script that comes with celery seems to favor a single instance on the box, so I'm wondering how people tend to config this?", "group_id": 81, "id": 1422680}, {"user_id": 281, "stars": [], "topic_id": 39679, "date_created": 1308358352.3696899, "message": "the supervisor config for each instance looks something like https://gist.github.com/1032673", "group_id": 81, "id": 1423989}, {"user_id": 281, "stars": [], "topic_id": 39679, "date_created": 1308358226.3868589, "message": "generally I've done this by having supervisord manage all my celeryd instances, the celeryd commands in the supervisor config are just calls to \"./manage.py celeryd\" with different options for different settings files passed each time", "group_id": 81, "id": 1423980}, {"user_id": 3580, "stars": [], "topic_id": 39679, "date_created": 1308358512.154037, "message": "ah, that's a good idea. I eventually sorted out the manage.py celeryd_multi command, and managed to get each of my envs going with pretty simple start/stop shells.. but plugging them into supervisor sounds like an awesome approach", "group_id": 81, "id": 1424002}]