From ac88e63c733f0aaf29946648869d871f2dd7144e Mon Sep 17 00:00:00 2001
From: hockeygoalie35 <hockeygoalie35@samulenas.com>
Date: Tue, 23 Apr 2024 23:21:25 -0400
Subject: [PATCH] Add Pushover and ntfy flags to config.conf

---
 lidarr/extended.conf | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/lidarr/extended.conf b/lidarr/extended.conf
index af2ffa6..e38805a 100644
--- a/lidarr/extended.conf
+++ b/lidarr/extended.conf
@@ -76,9 +76,14 @@ plexUrl=""   # ONLY used if PlexNotify.bash is used, example: http://x.x.x.x:324
 plexToken="" # ONLY used if PlexNotify.bash is used
 
 ##### DEEZER ARLCHECKER
-arlUpdateInterval='24h'    # Interval to check ARL Validity (default 24 hours). Reboot container after changing. s = seconds, m = minutes, h = hours, d = days
+arlUpdateInterval='24h'   # Interval to check ARL Validity (default 24 hours). Reboot container after changing. s = seconds, m = minutes, h = hours, d = days
 telegramBotEnable="false" # Enable/Disable  Telegram Bot to notify if ARL expires. Otherwise check text file in custom-services.d/python for status.
 telegramBotToken=""       # Get token from BotFather during bot creation. If you use a notify channel for Lidarr, you can probably use the same bot, as this script only takes temporary control.
 telegramUserChatID=""     # Get your userid by chatting: t.me/userinfobot
+pushoverEnable="false"    # Pushover Notification Support
+pushoverUserKey=""
+pushoverAppAPIKey=""
+ntfyEnable="false"             # ntfy Notification Support (Web Only, Maybe Self-Hosted to come?)
+ntfyTopic=""