This is a breaking change.

Changelog:
- Redis is now mandatory and enabled by default
- Added Sentinel, Standalone and Cluster support
- Standalone mode with sidecar is used by default
  - If no host(s) are configured, a redis sidecar is injected into the deployment
  - No extra configuration needed
  - This is intended for development and does not scale.
- Helm values have changed, see README.md:
  - `redis.host` has been renamed to `redis.hosts` and expects a list of strings with the following pattern: <localhost:6379> (needed for sentinel and cluster modes)
  - `redis.port` has been removed, see `redis.hosts`

- 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

michael.kainz authored 2 years ago and julian.baeume committed 2 years ago

This endpoint can be used to dynamically generate pwa.json based on configuration
on the java middleware.

root cause: When redis was not available, some files could not be saved in the local memory and therefore this error permanently occurs even though the node responded correctly.
solution: Improve robustness when redis is not available

Root cause: Circular dependency causes undefined function
Solution: As the registration of the listener can be async, just use a simple setTimeout

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