[Roadmap] background worker process

[SchrodingersGat]

We have been using django-q for ages, but the project has not received any updates in a few years.

There are also some shortcomings - in particular the tasks seem to run on multiple workers - see #4290

Perhaps it is time to migrate to something like celery:

• Better support (project is active)
• More comprehensive feature set
• Future proofing

I have not yet done the required reading to determine how difficult this might be, or if it would require using redis, etc.

[matmair]

@SchrodingersGat the thing I like about django q is that it does not need a broker to run. To my knowledge, we will need redis to use celery. Thus making testing and small bare metal setups harder.

[SchrodingersGat]

Indeed. I do like the simplicity of the current solution. Before switching I'd like to understand if there is a way around the current issues. The biggest one being the double execution of tasks

[SchrodingersGat]

Ref: Koed00/django-q#633
Ref: Koed00/django-q#577
Ref: Koed00/django-q#566

[matmair]

@SchrodingersGat can we close this now as #5167 is merged

[SchrodingersGat]

Yes, I think we can. Sticking with django-q is more attractive now that we've found an active fork