From 2ffa4a0a9c8bc2ce7ad22dcbc7d08ca1a1223a47 Mon Sep 17 00:00:00 2001
From: Matthew Rider <mattwr18@gmail.com>
Date: Mon, 15 Jul 2024 10:55:34 +0200
Subject: [PATCH] Favor telegram webhook method in development

---
 README.md                   | 11 +++++++++++
 docker-compose.override.yml |  4 ----
 2 files changed, 11 insertions(+), 4 deletions(-)

diff --git a/README.md b/README.md
index 4be42dac4..d500f33ec 100644
--- a/README.md
+++ b/README.md
@@ -76,6 +76,17 @@ We're using [our own fork](https://github.com/tactilenews/threema) of the `three
 bundle config local.threema .
 ```
 
+#### Telegram
+
+To test out Telegram webhooks, you need to first set the webhook. You can do this like so:
+
+```rb
+Telegram.bots_config
+{ <key>: <Telegram::Bot::Client> }
+bot = Telegram.bots[<key_of_bot>]
+bot.set_webhook(url: 'https://<localtunnel>/telegram/<route-to-telegram-bot>')
+```
+
 See this [blog post](https://rossta.net/blog/how-to-specify-local-ruby-gems-in-your-gemfile.html) for more information.
 
 ### Testing
diff --git a/docker-compose.override.yml b/docker-compose.override.yml
index c192e1687..d9d785324 100644
--- a/docker-compose.override.yml
+++ b/docker-compose.override.yml
@@ -17,10 +17,6 @@ x-dev-defaults: &x-dev-defaults
     - .:/app
 
 services:
-  telegram:
-    <<: *x-dev-defaults
-    command: rake telegram:bot:poller
-
   app:
     <<: *x-dev-defaults
     depends_on: [ db, mailserver, assets ]