Juan Esteban Aristizabal

Docker: run the celery worker in a separate container

2

Also consider moving the celery_app module from ``core/`` to ``worker/``. I think this makes much more sense because it is a completely separate component.

[minigramer/diagrams](https://github.com/mingrammer/diagrams)

Include: - [ ] How to setup the local build - [ ] How the scripts work

- [ ] different apps consume the same celery instance. - [ ] different apps consume the same rabbitmq instance. - [ ] different apps consume the same redis instance.

Consider: - [ ] [`asyncpg`](https://github.com/MagicStack/asyncpg) - [ ] [`tortois`](https://github.com/tortoise/tortoise-orm) - [ ] [``SqlAlchemy`` asynchronous I/O features](https://docs.sqlalchemy.org/en/14/orm/extensions/asyncio.html): this one might be the less invasive option. Since the app is already using...