Add Celery

[0xAda]

We need to add celery

• clean up preevent cache generation
• email sending
• various events we might want to handle on event open/end
• discord webhooks

[thebeanogamer]

We keep talking about adding Celery, and we should probably bite the bullet and do it. Being able to schedule background jobs will have other uses we should probably document here.

[thebeanogamer]

@jerbob I defer to you here, but presumably this means we're going to need to add another container? We need to consider how that works with self-hosted instances, perhaps a job for the RACTF public address system? Would probably involve us having to write a migration tool for Docker Compose files into ractl...

I don't really want to do the hacky solution of running this as a background process in the backend container.

[jerbob]

Ye s to cobfirm we need another container

[jerbob]

The same way we used to start two instances for ASGI+WSGI

[thebeanogamer]

We still do

[jerbob]

no no nonono wait wait wait wait wait

[0xAda]

wait why are we still starting two containers?

[thebeanogamer]

If we're going to change this, it should probably be its own issue

[jerbob]

I think we fixed that bug in app-restructure

[0xAda]

I think we fixed that bug in app-restructure

Doesn't look like it, docker-compose.yml still has sockets and web

[jerbob]

I think we fixed that bug in app-restructure

Doesn't look like it, docker-compose.yml still has sockets and web

Okay, we should only need a single container to handle HTTP + websockets but I suppose that's out of scope for this ticket.

[jchristgit]

I have been fortunate to have used celery as part of previous employment in the past two years, and I have come to the conclusion that we must not, under any circumstances, use celery. I can provide reasons if interested.