convore.json/groups/django-community/celery-deploymentconfig-practices/messages.json

[{"user_id": 3580, "stars": [], "topic_id": 14351, "date_created": 1300756261.204423, "message": "so presumably heavy use of virtual-envs for the worker's space is a big part of running celery?", "group_id": 81, "id": 404177}, {"user_id": 3580, "stars": [], "topic_id": 14351, "date_created": 1300756229.18701, "message": "interesting. that makes sense.", "group_id": 81, "id": 404176}, {"user_id": 3580, "stars": [], "topic_id": 14351, "date_created": 1300755920.6248331, "message": "Looking into standing up celery (never used it before)... one of the things I'm trying to wrap my head around is the deployment model for celery on an instance that runs multiple versions of my app.", "group_id": 81, "id": 404141}, {"user_id": 1736, "stars": [], "topic_id": 14351, "date_created": 1300755962.914542, "message": "Do you want to use a single queue broker for all of them?", "group_id": 81, "id": 404150}, {"user_id": 1736, "stars": [], "topic_id": 14351, "date_created": 1300756146.6997671, "message": "Yes, each will definitely need its own workers", "group_id": 81, "id": 404168}, {"user_id": 1736, "stars": [], "topic_id": 14351, "date_created": 1300756195.5955651, "message": "Not sure about the result backend, but that should be fine since task instances are keyed by UUID", "group_id": 81, "id": 404174}, {"user_id": 3580, "stars": [], "topic_id": 14351, "date_created": 1300756611.978184, "message": "oooh. okay, that makes loads of sense. hadn't noticed that running it w/ manage.py was an option :)", "group_id": 81, "id": 404194}, {"user_id": 1736, "stars": [], "topic_id": 14351, "date_created": 1300755973.6410029, "message": "(ex. a single RAbbitMQ instance)", "group_id": 81, "id": 404153}, {"user_id": 1736, "stars": [], "topic_id": 14351, "date_created": 1300756459.391624, "message": "Yes, usually you run the worker via Django's manage.py to make that easy", "group_id": 81, "id": 404186}, {"user_id": 3580, "stars": [], "topic_id": 14351, "date_created": 1300756002.450876, "message": "well.. I'm not sure. That seems problematic when it comes to writing tasks that use my django models, etc.. right?", "group_id": 81, "id": 404159}, {"user_id": 3580, "stars": [], "topic_id": 14351, "date_created": 1300756044.5170159, "message": "unless my mental model is broken.. seems like Celery needs my django app to be on it's sys.path, and since I have multiple versions of my app on the host.. I won't be able to re-use a celery instance across them, right?", "group_id": 81, "id": 404163}, {"user_id": 3580, "stars": [], "topic_id": 14351, "date_created": 1300756062.6909549, "message": "oh, I do want to use a single Redis instance to back all of them though, yes.", "group_id": 81, "id": 404165}, {"user_id": 1736, "stars": [], "topic_id": 14351, "date_created": 1300756171.7746511, "message": "but you might be able to configure it so that they share a single queue", "group_id": 81, "id": 404172}, {"user_id": 3580, "stars": [], "topic_id": 14351, "date_created": 1300756273.962312, "message": "(since it's config, and my app both end up needing to be on it's path)", "group_id": 81, "id": 404178}, {"user_id": 1736, "stars": [], "topic_id": 14351, "date_created": 1300756490.9011221, "message": "Celery doesn't live independently from Django, it is just part of your app", "group_id": 81, "id": 404188}, {"user_id": 1736, "stars": [], "topic_id": 14351, "date_created": 1300756496.6649821, "message": "just like with gunicorn", "group_id": 81, "id": 404189}, {"user_id": 1736, "stars": [], "topic_id": 14351, "date_created": 1300756652.196877, "message": "Yep, also celerybeat and the camera daemon", "group_id": 81, "id": 404195}, {"user_id": 3580, "stars": [], "topic_id": 14351, "date_created": 1300773518.4665539, "message": "@coderanger Spent the last couple hours digging in (and getting sidetracked by a wacky Celery bug).. but I'm thinking I've misunderstood Redis support based on the source I'm reading (v 2.2.4)... It doesn't look like broker_connection() has any implementations other than the AppBase amqp connection creator.", "group_id": 81, "id": 405107}, {"user_id": 3580, "stars": [], "topic_id": 14351, "date_created": 1300773547.1693931, "message": "I was thinking I could back Redis without an amqp server at all. No?", "group_id": 81, "id": 405109}, {"user_id": 1736, "stars": [], "topic_id": 14351, "date_created": 1300776901.0217791, "message": "The docs used to have examples of setting this up, Paging @asksol on line 1 :-)", "group_id": 81, "id": 405254}, {"user_id": 1736, "stars": [], "topic_id": 14351, "date_created": 1300776879.9898901, "message": "@phill You can, look at Kombu's virtual transports. I use Redis as both the queue broker and results backend.", "group_id": 81, "id": 405250}, {"user_id": 6431, "stars": [{"date_created": 1300854171.4228971, "user_id": 1736}], "topic_id": 14351, "date_created": 1300848841.7327001, "message": "@phill fwiw, we're running celeryd off manage.py with supervisord. The combo's been good so far.", "group_id": 81, "id": 413624}]