since quite some time we do not report the pod as unhealthy any longer
if redis connection is gone. So in case the connection is lost, we want it
to reconnect.

Make sure to always fetch from redis once client (re-)connected.

julian.baeume authored 1 year ago and julian.baeume committed 1 year ago

Changelog:
- introduce two separate roles for middleware deployments:
    - ui-middleware: read from redis only, listen to version updates, can easily be scaled
    - updater: split out all code that writes to redis, no need to scale > 1

- Unit and Integration tests now use "inject" instead of starting a server
  and using supertest.
- Add Coverage Reports and "test:dev" mode. This enables a mocha --watch
  like workflow using nodemon, as --watch does not work with esm modules.
- Reorganized and renamed files and functions

richard.petersen authored 2 years ago and julian.baeume committed 2 years ago

Root cause: Due to a bunch of redis restarts, the bull-queues got unregistered and did not register again.
Solution: On every reconnect, readd the bull queue again.

alexander.quast authored 2 years ago and richard.petersen committed 2 years ago

Changelog:
 - Changed all 'trace' logs to level 'debug'
 - Added logging to the version check functions on log level 'info' and 'debug'
 - Added some time measures on ready checks to see what's taking so long on startup

this can not only be handled on ingress level, but we need to mount the
express app also on the app root level. This basically just works out of the
box.

julian.baeume authored 3 years ago and julian.baeume committed 3 years ago

since it's still kind of small, it makes sense to switch to ESM, now.