Backend services for traffic lights (from #1035)

m2ms / fragalysis-frontend

The React, Redux frontend built by webpack

Other

1 stars 1 forks source link

Backend services for traffic lights (from #1035) #1205

Open kaliif opened 10 months ago

kaliif commented 10 months ago

how long in that state (should backend supply that?)

Yes, this needs to come from backend or we can track it for each user session (when user loads the page it will start counting for each service and when a state will change it will reset the counter and so)

Originally posted by @matej-vavrek in https://github.com/m2ms/fragalysis-frontend/issues/1035#issuecomment-1809841716

Changes in backend are going to be rather substantial, needs to remember the state. Probably best to solve this with service/job that's launched on startup and stores the service states in a table.

phraenquex commented 10 months ago

@kaliif I've assigned tags and a project - all new tickets need to have tags and project.

I imagine this stays in the dark-teal release, but maybe it should go into the V2 backlog. @Waztom help decide at meeting tomorrow.

mwinokan commented 4 months ago

This is needed for #1359

kaliif commented 4 months ago

@alanbchristie @boriskovar-m2ms @matej-vavrek, when writing this, I added celery beat to local environment. I left the main compose file unchanged, but should you need asynchronous celery tasks as well, the additional compose file with beat containers can be run as:

docker compose -f docker-compose.yml -f docker-compose.celery.yml up

alanbchristie commented 4 months ago

The change has improved the number of M<ySQL queries that are now made. You can see the before (pre-16:30) and after (post-16:30) in this grafana screenshot...