docs: document scoped systemd service names for multi-install
- Update messaging guide to use 'hermes gateway' CLI commands instead of raw systemctl (auto-resolves the correct service name) - Add info callout explaining multi-install service name scoping - Update HERMES_HOME env var docs to mention PID + service name scoping
This commit is contained in:
parent
30da22e1c1
commit
51185354dd
2 changed files with 9 additions and 5 deletions
|
|
@ -34,7 +34,7 @@ All variables go in `~/.hermes/.env`. You can also set them with `hermes config
|
||||||
| `VOICE_TOOLS_OPENAI_KEY` | Preferred OpenAI key for OpenAI speech-to-text and text-to-speech providers |
|
| `VOICE_TOOLS_OPENAI_KEY` | Preferred OpenAI key for OpenAI speech-to-text and text-to-speech providers |
|
||||||
| `HERMES_LOCAL_STT_COMMAND` | Optional local speech-to-text command template. Supports `{input_path}`, `{output_dir}`, `{language}`, and `{model}` placeholders |
|
| `HERMES_LOCAL_STT_COMMAND` | Optional local speech-to-text command template. Supports `{input_path}`, `{output_dir}`, `{language}`, and `{model}` placeholders |
|
||||||
| `HERMES_LOCAL_STT_LANGUAGE` | Default language passed to `HERMES_LOCAL_STT_COMMAND` or auto-detected local `whisper` CLI fallback (default: `en`) |
|
| `HERMES_LOCAL_STT_LANGUAGE` | Default language passed to `HERMES_LOCAL_STT_COMMAND` or auto-detected local `whisper` CLI fallback (default: `en`) |
|
||||||
| `HERMES_HOME` | Override Hermes config directory (default: `~/.hermes`) |
|
| `HERMES_HOME` | Override Hermes config directory (default: `~/.hermes`). Also scopes the gateway PID file and systemd service name, so multiple installations can run concurrently |
|
||||||
|
|
||||||
## Provider Auth (OAuth)
|
## Provider Auth (OAuth)
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -244,10 +244,10 @@ Background tasks on messaging platforms are fire-and-forget — you don't need t
|
||||||
|
|
||||||
```bash
|
```bash
|
||||||
hermes gateway install # Install as user service
|
hermes gateway install # Install as user service
|
||||||
systemctl --user start hermes-gateway
|
hermes gateway start # Start the service
|
||||||
systemctl --user stop hermes-gateway
|
hermes gateway stop # Stop the service
|
||||||
systemctl --user status hermes-gateway
|
hermes gateway status # Check status
|
||||||
journalctl --user -u hermes-gateway -f
|
journalctl --user -u hermes-gateway -f # View logs
|
||||||
|
|
||||||
# Enable lingering (keeps running after logout)
|
# Enable lingering (keeps running after logout)
|
||||||
sudo loginctl enable-linger $USER
|
sudo loginctl enable-linger $USER
|
||||||
|
|
@ -263,6 +263,10 @@ Use the user service on laptops and dev boxes. Use the system service on VPS or
|
||||||
|
|
||||||
Avoid keeping both the user and system gateway units installed at once unless you really mean to. Hermes will warn if it detects both because start/stop/status behavior gets ambiguous.
|
Avoid keeping both the user and system gateway units installed at once unless you really mean to. Hermes will warn if it detects both because start/stop/status behavior gets ambiguous.
|
||||||
|
|
||||||
|
:::info Multiple installations
|
||||||
|
If you run multiple Hermes installations on the same machine (with different `HERMES_HOME` directories), each gets its own systemd service name. The default `~/.hermes` uses `hermes-gateway`; other installations use `hermes-gateway-<hash>`. The `hermes gateway` commands automatically target the correct service for your current `HERMES_HOME`.
|
||||||
|
:::
|
||||||
|
|
||||||
### macOS (launchd)
|
### macOS (launchd)
|
||||||
|
|
||||||
```bash
|
```bash
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue