feat: add messaging gateway startup functionality
- Introduced a new function to check for configured messaging platform tokens and prompt the user to start the gateway. - Updated the installation scripts to automatically start the gateway if messaging tokens are detected, enhancing user experience. - Expanded the README to include instructions for starting the gateway, ensuring users are informed about the necessary steps for message handling.
This commit is contained in:
12
README.md
12
README.md
@@ -85,6 +85,18 @@ All your settings are stored in `~/.hermes/` for easy access:
|
||||
└── logs/ # Logs
|
||||
```
|
||||
|
||||
### Messaging Platforms (Telegram, Discord, Slack)
|
||||
|
||||
If you configured a messaging bot token during setup, **start the gateway** so Hermes can receive and send messages:
|
||||
|
||||
```bash
|
||||
hermes gateway # Run in foreground (see output)
|
||||
hermes gateway install # Or install as a background service (Linux)
|
||||
hermes gateway start # Start the background service
|
||||
```
|
||||
|
||||
The installer will offer to do this automatically if it detects a bot token. See [Messaging Gateway](#messaging-gateway) below for full setup instructions.
|
||||
|
||||
### Managing Configuration
|
||||
|
||||
```bash
|
||||
|
||||
Reference in New Issue
Block a user