v.2.5.1 - hotfix for stacking notifications on reload

Major

• Since changing notifications to an array they would start stacking up on reload (when config changes), this is now fixed.

---

Full Changelog: v2.5.1...v.2.5.2

v2.5.1 - hotfix for last release

Major

• Reverted a line before committing last release and didn't notice, derp. This prevented the actual event notifications from sending.

v2.5 - Notifications overhaul.

Major

• Change discord module to allow multiple instances (OO).
• Allow multiple notifications to multiple sources.
• Create three tiers of notifications.
• Implemented two, heh. Debug there if needed.
• Add precedence to matching, allows for multiple regex matches to be sorted to desired match.

Full Changelog: v2.4...v2.5

Next, would like to allow more notification types.

v2.4 - File::Monitor support added.

Changes

Major

• Add support for File::Monitor so we can watch the config file and reload it automatically if desired. Now you don't have to always reload it with signals in daemon mode.

v2.3 - Fix Notifications Bug, Minor Clean Up

Changes

Major

• Fix bug where notifications would 'multiply' on reload, adjusted config layout to avoid this (adding type field to each notification), then changed the storage from an array to a hash, so that on reload the entries get updated. This isn't perfect as if you delete a notification and reload, it'll stay there until a full daemon restart. It does allow you to change existing ones with a reload though.

Minor

• Remove all the exports from modules except for meta and data in the config module.
• Added a sample service file for systemd.
• Adjusted the sample config for the notification bug fix.
• Update README.md to be more inline with the current config (could use a full re-write though).

v2.0(ish) - Fairu-chan glow up!

The important points!

• Total code refactor.
• Fully annotated sample configuration file.
• SIGNALS and daemon mode!
  • SIGUSR1 will check for new files and action instead of waiting for the idleTime
  • SIGUSR2 will rescan and install a new configuration if it is found to be valid
  • SIGTERM will gracefully exit
  • SIGINT will exit in a most ungraceful way as always
• Added back "mapping functions" from rename.pl (where this all started, it's in a Gist), these allow you to modify the incoming data before it gets stuffed into the output file name.

v1.0 - Fairu-chan!

Debugged, config validation added, README is comprehensive-ish, and sample config has some comments!

Been running on my Plex server for about a full week now with no issues.

Cheers,
Justin.