require 'sequel' module NotificationServices module Models # :iid - primary_key # :id - String (indexed) # :url - String class Webhook < Sequel::Model one_to_many :triggers end # :iid - primary_key # :trigger - String class Trigger < Sequel::Model many_to_one :webhook end end end
# | Change | User | Description | Committed | |
---|---|---|---|---|---|
#5 | 13972 | tjuricek |
Removing old microservice implementations. The system is now mostly a monolith. Eventually there will be a websocket service. |
||
#4 | 13677 | tjuricek | Fixed issues with Sequel saving and displaying webhooks in notification_services. | ||
#3 | 13470 | tjuricek |
Phoenix notification services, client API, including new phoenix_updater This is an interim commit containing a first pass implementation of the phoenix_updater. Notably missing parts: - The Qt API doesn't yet actually interact with the phoenix_updater - The phoenix_services web service doesn't filter out notifications I *may* end up creating another web application *just* to filter out notifications, since this may end up taking up a lot of background workers. |
||
#2 | 13469 | tjuricek |
Initial implementation of change-commit notification services. Set up a new database just for storing webhook configuration for the notification services. It uses the stable version of Resque, which needs to be evaluated in more detail. This should be easier for an admin to monitor than something like Sidekiq, but performance evaluation needs to happen before production release. No automated tests yet, that will rely upon a Phoenix notification mechanism existing first. |
||
#1 | 13468 | tjuricek | Set up resque worker that will trigger web hooks in the background. |