Closed glowing-axolotl closed 1 year ago
Closing as already fixed 4 days ago by https://github.com/kaleidos-ventures/taiga-docker/commit/e6af1448b4a7ba4a5e22785ab507500cf38b45e6 (didn't notice as we were still testing the modification and only today got to resolve the conflicts with the main branch). See https://github.com/kaleidos-ventures/taiga-docker/issues/44 for more info.
This fixes https://github.com/kaleidos-ventures/taiga-docker/issues/44 "[BUG] taiga-events_1 container failing #44", where the service taiga-events would start up before the required container taiga-events-rabbitmq was in ready status, resulting in a failure of the taiga-events-***** container every time a docker-compose up was run.
With the following changes taiga-events will wait until the taiga-events-rabbitmq service is completely healthy before starting. This also means the docker compose up command will wait for the rabbitmq container to be in a healthy state, as well as the containers that depend on taiga-events such as taiga-back and taiga-gateway. From our tests this means it will wait about 30 seconds every time the docker compose up is run.