From 56aa1b2b1fb30251dc77d34f658148a5cbe83263 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?P=C4=93teris=20Caune?= Date: Tue, 2 Jan 2018 15:29:35 +0200 Subject: [PATCH] Document `settelegramwebhook` in README, and 2017->2018 --- README.md | 18 +++++++++--------- templates/base.html | 2 +- templates/emails/base.html | 2 +- 3 files changed, 11 insertions(+), 11 deletions(-) diff --git a/README.md b/README.md index 17a8ade7..2ddfafbb 100644 --- a/README.md +++ b/README.md @@ -249,14 +249,14 @@ description, user picture, and add a "/start" command. * After creating the bot you will have the bot's name and token. Add them to your `hc/local_settings.py` file as `TELEGRAM_BOT_NAME` and `TELEGRAM_TOKEN` fields. -* Now the tricky part: when a Telegram user talks to your bot, -Telegram will use a webhook to forward received messages to your healthchecks -instance. For this to work, your healthchecks instance needs to be publicly -accessible over HTTPS. Using the -[setWebhook](https://core.telegram.org/bots/api#setwebhook) API call -set the bot's webhook to `https://yourdomain.com/integrations/telegram/bot/`. - - - +* Run `settelegramwebhook` management command. This command tells Telegram +where to forward channel messages by invoking Telegram's +[setWebhook](https://core.telegram.org/bots/api#setwebhook) API call: + ``` + $ ./manage.py settelegramwebhook + Done, Telegram's webhook set to: https://my-monitoring-project.com/integrations/telegram/bot/ + ``` +For this to work, your `SITE_ROOT` needs to be correct and use "https://" +scheme. diff --git a/templates/base.html b/templates/base.html index e2d15bcc..794910a4 100644 --- a/templates/base.html +++ b/templates/base.html @@ -161,7 +161,7 @@