Refactor redis
and queue dependencies in preparation for Django 4.0
#486
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
After this PR, it should be hopefully straightforward to migrate to Django 4.0 (will send in a follow-up PR).
We need to perform special operations on production to make it work with this PR!
Ideally by stopping the server, performing the migration steps manually, and then restarting it and let the after-merge deploy be a no-op.
What needs to be done:
--with-scheduler
flag for thedefault
queue:rqworker default --with-scheduler
rqscheduler
serviceSCHEDULER_QUEUES
inlocal_settings.py
(needs to be done with admin access)scheduler
migrations: