Various Enhancements and features

[yatharthranjan]

• Remove all scheduled tasks when a FCM token unregistered (i.e. app uninstalled or new token issued)
  • Use more caching and performance improvements
  • Add tests for testing the server under different loads (No end-to-end test though)
  • Improves exception handling
  • Re-enables the cancel functionality as required when timezone changes/ schedule re-generated in aRMT
  • Adds sound parameter to notification payload as some devices reported no sound on notification delivery
  • Also add server mode to the list of available scheduler options so as to allow concurrent access to the database (Can build a simple UI on top of it for checking notifications in the future)
  • Adds docker-compose file for the XMPP-server and database server and Dockerfile for building and running hsql database server

[afolarin]

Looks great :+1: - these are nice improvements.

I was thinking perhaps a persisting the delivered schedule for a configurable length of time for schedule provenance

[yatharthranjan]

@afolarin Yes that can be done. will that be required when the server sends delivery info to kafka too ? (Since i have already started implementing that)

[afolarin]

@yatharthranjan no it won't. Go ahead with the current implementation