wiki: publish pending edits (2026-10-20)
This commit is contained in:
@@ -3,8 +3,8 @@ title: Multiplexer Setup (Multi-Profile Gateway)
|
||||
type: runbook
|
||||
status: active
|
||||
created: 2026-07-28
|
||||
updated: 2026-07-28
|
||||
verified_on: 2026-07-28
|
||||
updated: 2026-10-20
|
||||
verified_on: 2026-10-20
|
||||
confidence: high
|
||||
tags: [hermes, multiplexer, telegram, profiles, gateway]
|
||||
---
|
||||
@@ -67,6 +67,28 @@ platforms:
|
||||
enabled: false # ← DISABLED — multiplexer handles this
|
||||
```
|
||||
|
||||
## ⚠ The `ops` profile was DELETED on 2026-10-11 (verified 2026-10-20)
|
||||
|
||||
`/home/hermes/.hermes/profiles/` now contains **only** `.deleted/ops` (an 8-byte marker file whose
|
||||
entire content is the word `deleted`, dated 2026-10-11). **`~/.hermes/profiles/ops/` no longer
|
||||
exists** — there is no `config.yaml`, no `SOUL.md`, no profile directory.
|
||||
|
||||
**But the default profile still routes to it.** `~/.hermes/config.yaml` still carries both
|
||||
`profile_routes` entries (`ops-group` → `-1003914987043`, `ops-group-2` → `-1003932503629`,
|
||||
both `profile: ops`), and `multiplex_profiles: true` is still set. The ops SOUL (Tusk, the African
|
||||
elephant) and its `allowed_chats` list are gone with the directory.
|
||||
|
||||
**Consequence:** messages arriving in the two ops chats have a route pointing at a profile that no
|
||||
longer exists. Treat the "Ops profile" blocks below as **historical** — the second profile's
|
||||
config can no longer be read at `~/.hermes/profiles/ops/config.yaml` because that path is gone.
|
||||
|
||||
**Two things need a decision (not actioned here):**
|
||||
1. Should `profile_routes` be removed, or should the `ops` profile be recreated?
|
||||
2. Is the `multiplex_profiles: true` + two-route configuration still needed at all?
|
||||
|
||||
Until that is settled, treat the ops chat IDs as **possibly unroutable** and verify the gateway
|
||||
actually resolves them before relying on this runbook.
|
||||
|
||||
## The Silent-Drop Pitfall
|
||||
|
||||
The `allowed_chats` gate runs on the **default profile's adapter** BEFORE `profile_routes` stamps `source.profile`. If a chat is only authorized in the secondary profile's config but not the default's, messages from that chat are silently dropped.
|
||||
|
||||
Reference in New Issue
Block a user