Starting to implement alerts #17

config-example.yml

@@ -6,13 +6,13 @@
 # this as "N0CALL" and it shouldn't do any harm, as we're not sending anything to the various networks, only receiving.
 server-owner-callsign: "N0CALL"
 
-# Data providers to use. This is an example set, tailor it to your liking by commenting and uncommenting.
+# Spot providers to use. This is an example set, tailor it to your liking by commenting and uncommenting.
 # RBN and APRS-IS are supported but have such a high data rate, you probably don't want them enabled.
 # Each provider needs a class, a name, and an enabled/disabled state. Some require more config such as hostnames/IP
 # addresses and ports. You can duplicate them if you like, e.g. to support several DX clusters. RBN uses two ports, 7000
 # for CW/RTTY and 7001 for FT8, so if you want both, you need two entries, as shown below.
 # Feel free to write your own provider classes! There are details in the README.
-providers:
+spot-providers:
   -
     class: "POTA"
     name: "POTA"
@@ -62,11 +62,20 @@ providers:
     enabled: false
     port: 7001
 
+# Alert providers to use. Same setup as the spot providers list above.
+alert-providers:
+  -
+    class: "POTA"
+    name: "POTA"
+    enabled: true
+
 # Port to open the local web server on
 web-server-port: 8080
 
-# Maximum spot age to keep in the system before deleting it
+# Maximum time to keep spots and alerts in the system before deleting them. By default, one hour for spots and one week
+# for alerts.
 max-spot-age-sec: 3600
+max-alert-age-sec: 604800
 
 # Login for QRZ.com to look up information. Optional.
 qrz-username: "N0CALL"