forked from NodyHub/flathunter
-
Notifications
You must be signed in to change notification settings - Fork 22
/
config.yaml.dist
50 lines (44 loc) · 1.46 KB
/
config.yaml.dist
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
# Should the bot endlessly looop through the URLs?
# Between each loop it waits for <sleeping_time> seconds.
loop:
active: yes
sleeping_time: 60
# List the URLs containing your filter properties below.
# Currently supported services: www.immobilienscout24.de,
# www.wg-gesucht.de.,ebay-kleinanzeigen.de, immowelt.de
# List the URLs in the following format:
# urls:
# - https://www.immobilienscout24.de/Suche/...
# - https://www.wg-gesucht.de/...
#
# IMMOWELT: Always sort after newest entries, => ?sort=createdate
urls:
# Multiline message (yes, the | is supposed to be there),
# to format the message received from the Telegram bot.
#
# Available placeholders:
# - {title}: The title of the expose
# - {rooms}: Number of rooms
# - {price}: Price for the flat
# - {url}: URL to the expose
message: |
{title}
Zimmer: {rooms}
Größe: {size}
Preis: {price}
{url}
# Sending messages using Telegram requires a Telegram Bot configured.
# Telegram.org offers a good documentation about how to create a bot.
# Once you read it, will make sense. Still: bot_token should hold the
# access token of your bot and receiver_ids should list the client ids
# of receivers. Note that those receivers are required to already have
# started a conversation with your bot.
#
# telegram:
# bot_token: 160165XXXXXXX....
# receiver_ids:
# - 12345....
# - 67890....
telegram:
bot_token:
receiver_ids: