From de7a6be9fec2944d85be81e21c30aec734bff7a7 Mon Sep 17 00:00:00 2001 From: Gerard Ribas Canals Date: Fri, 13 Oct 2017 10:17:01 +0200 Subject: [PATCH] Telegram Notifications --- duplicity-backup.conf.example | 4 ++++ duplicity-backup.sh | 3 +++ 2 files changed, 7 insertions(+) diff --git a/duplicity-backup.conf.example b/duplicity-backup.conf.example index 0a0dc99..0391982 100644 --- a/duplicity-backup.conf.example +++ b/duplicity-backup.conf.example @@ -439,6 +439,10 @@ IFTTT_MAKER_EVENT="duplicity" # name the event to trigger at IFTTT Maker Channel IFTTT_HOOK_URL="https://maker.ifttt.com/trigger/$IFTTT_MAKER_EVENT/with/key/$IFTTT_KEY" # ONLY change this if IFTTT changes it IFTTT_VALUE2="" # general purpose value to pass to your maker channel (optional) +# Provider: Telegram +TELEGRAM_CHATID="" #Generate a Telegram bot following guide: https://core.telegram.org/bots#3-how-do-i-create-a-bot +TELEGRAM_KEY="" + # ------------------------------------------------------------------------------ # TROUBLESHOOTING # ------------------------------------------------------------------------------ diff --git a/duplicity-backup.sh b/duplicity-backup.sh index 739fab3..ee4c6a8 100755 --- a/duplicity-backup.sh +++ b/duplicity-backup.sh @@ -569,6 +569,9 @@ send_notification() -F "message=${NOTIFICATION_CONTENT}" \ https://api.pushover.net/1/messages echo -e "Pushover notification sent" + elif [ "${NOTIFICATION_SERVICE}" = "telegram" ]; then + curl -s --max-time 10 -d "chat_id=$TELEGRAM_CHATID&disable_web_page_preview=1&text=$NOTIFICATION_CONTENT" "https://api.telegram.org/bot$TELEGRAM_KEY/sendMessage" >/dev/null + echo -e "Telegram notification sent" fi fi }