Support disabling auto-purge

Support disabling auto-purge by specifying a purgeInterval of 0. Resolves issue 399.

Fix failed to start issue with new secrets system

Resolve an issue where the system fails to start if no secrets file exists but the existing settings.json or triggers.json file uses mustache templates, or when the secrets method of loading the settings file isn't used.

Add support for external secrets

• Secrets can now be stored in a separate secrets.json file and inserted in settings.json and triggers.json via mustache templates. Resolves
  issue 371.
• Update a package dependency to resolve a security vulnerability.

Add support for activateRegions

Triggers can now specify activateRegions which have the opposite effect of masks. If activateRegions are specified then the triggering object's bounding box must overlap with the activate region for the trigger to fire.

See the defining triggers documentation for more details.

Network shared image folders work on Macs

File watching now works on Macs when the folder of images is a mounted network share. Resolves issue 362.

Enable viewing contents of originals and annotation folders

The /originals and /annotations folders can now be viewed via the webserver. This enables browsing the list of all stored images instead of having to know the specific filename of the image. Resolves issue363.

Minor security patches

• Address security vulnerability in webpack used during the build process. Resolves issue 357.
• Address security vulnerability in the annotated image processing library. Resolves issue 360.

Store original files after trigger fires

• The original image that caused a trigger to fire is now stored temporarily and available for use via the built-in web server. The images are available in the /originals folder with the original filename. Resolves issue 350.

Address a security vulnerability in a 3rd party library

• Address a low-severity security vulnerability in a 3rd party library.

Change watchObject folder verification to a warning

• Relax the test for valid watchObject folders at startup. If the path has globs in it a warning will still get thrown but system startup will proceed. Resolves issue 342.