drifty/twitchrise-bot
1
0
Fork 0
mirror of https://github.com/driftywinds/twitchrise-bot.git synced 2025-12-20 12:03:56 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update README.md

Browse Source
This commit is contained in:
drifty
2025-08-09 20:02:40 +05:30
committed by GitHub
parent 4e2e916655
commit ec7c1262b2
1 changed files with 5 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
README.md
View File

@@ -7,6 +7,11 @@ Twitchrise uses an ```.env``` to define variables and is only catered for a sing
- Add channel to monitor (```/add <channelname>```) - Add channel to monitor (```/add <channelname>```)
- Remove channels to monitor (```/remove <channelname>```) - Remove channels to monitor (```/remove <channelname>```)
- List all the channels they have added to monitor (```/list```) - List all the channels they have added to monitor (```/list```)
- Add additional Apprise endpoints (```/setapprise <URL>```)
- Remove added Apprise endpoints (```/rmapprise <number>```)
- List added Apprise endpoints (```/listapprise```)
Apprise endpoints and their formats can be seen [here](https://github.com/caronc/apprise#supported-notifications).
The bot admin can define the interval in seconds the bot will poll Twitch to check if the channels are live or not in the ```.env``` file. Although this restricts the usage of Twitchrise primarily through Telegram, I am a fan of Telegram and use it in my workflow extensively enough to warrant this usecase. The bot admin can define the interval in seconds the bot will poll Twitch to check if the channels are live or not in the ```.env``` file. Although this restricts the usage of Twitchrise primarily through Telegram, I am a fan of Telegram and use it in my workflow extensively enough to warrant this usecase.