feat: Telegram Servicer #15
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This module provides an Telegram bot API to interact with the user
without a direct access to Home Security Service.
Main responsibilities of the servicer as follows:
- Bot provides if hardware and the bot itself is alive. (/alive)
- Bot provides if the service is dead or alive. (/health hss.service)
- Bot restarts the service if the command is sent. (/restart hss.service)
- Bot provides the latest N logs if wanted. (/logs hss.service:N)
- Bot provides if protectors are in house, and whose. (/inhouse)
- Bot provides an image-shot if wanted. (/imageshot)
- Bot schedules a reboot for the hardware. (/reboot)
- Bot provides a shell access to the hardware. (/shell)