Bot will not restart if network connectivity is lost about makibot HOT 2 CLOSED

Merged in #110 something that may fix this. Need to keep this opened in case it doesn't fix it.

from makibot.

#151 seems to fix this issue. The following snippet was added to the docker-compose that manages the main instance running in production:

healthcheck:
  test: wget -qO- http://localhost:8080/healthcheck
  interval: 30s
  timeout: 10s
  retries: 3

Recently some correlations between users whose !accept request was ignored by the bot and the restart schedule for the bot have confirmed unless the contrary is said, that whenever the bot loses connectivity, its status changes from READY to something else, although it hasn't been confirmed because of the lack of logging events made by the bot.

This issue will be closed and marked as fixed unless we see it happening again.

from makibot.