Considerations for mixed Django & Celery versions

8 views
Skip to first unread message

Mike Lissner

unread,
Apr 16, 2019, 7:21:46 AM4/16/19
to Django users
We've currently running django 1.8.x and Celery 3.1.19 in production and our code base is getting a little too big. To fix this, our plan is to pull out Celery tasks into a separate repo and docker image.

As we do this, it'd be nice if we could upgrade both Django and Celery to their latest versions since obviously we've been bad about that.

I'll be manually copy/pasting models (and their changes) from one repo to the other to keep them in sync (some tasks read/write to the DB). I don't imagine the model file format has changed nor the expectations for what the underlying DB would look like.

Are there any major concerns to have if you're running different Django and Celery versions like this?

Reply all
Reply to author
Forward
0 new messages