wiki: publish pending edits (2026-10-20)
This commit is contained in:
@@ -3,8 +3,8 @@ title: Backups
|
||||
type: infrastructure
|
||||
status: active
|
||||
created: 2026-07-22
|
||||
updated: 2026-07-22
|
||||
verified_on: 2026-07-22
|
||||
updated: 2026-10-20
|
||||
verified_on: 2026-10-20
|
||||
confidence: medium
|
||||
tags: [infrastructure, backups]
|
||||
sources: [raw/configs/hermes-config-sanitized.txt]
|
||||
@@ -33,6 +33,21 @@ How Hermes's own configuration/state gets backed up, and what's missing.
|
||||
|
||||
## Known gaps
|
||||
- **No scheduled backup job found:** `crontab -l -u hermes` returns empty, and no systemd timer references `hermes` or `backup`. The one full backup on disk appears to have been triggered manually, not on a schedule.
|
||||
|
||||
> **Re-verified 2026-10-20 — the gap is unchanged and the single backup is now 90 days old.**
|
||||
> - `crontab -l -u hermes` → "no crontab for hermes". `systemctl --user list-timers --all` → **0 timers**.
|
||||
> The only timer on the box is the system-level `dpkg-db-backup.timer` — nothing Hermes-related.
|
||||
> - The one full backup is still `/home/hermes/hermes-backup-2026-07-22-180830.zip` (246 MB, dated
|
||||
> 22 Jul). **No new full backup has been taken in the 90 days since.**
|
||||
> - `/home/hermes/hermes-wiki/` is still **empty**; `/home/hermes/wiki-personal-backups/` still holds
|
||||
> only the four original 22 Jul files (`current-state.md`, `index.md`, `log.md`, `SCHEMA.md`).
|
||||
> - `~/.hermes/scripts/mnemosyne-backup.sh` still exists (unchanged since 3 Jul).
|
||||
> - `updates:` in `config.yaml` still reads `pre_update_backup: false`, `backup_keep: 5`,
|
||||
> `non_interactive_local_changes: stash`.
|
||||
>
|
||||
> **The separate wiki backup is also unrun:** `/home/hermes/wiki-backups/` does not exist, so the
|
||||
> tarball step in [[runbooks/backup-wiki]] has never been executed (the runbook's `mkdir -p` would
|
||||
> create it on first use).
|
||||
- `pre_update_backup: false` means an in-place `hermes update` will not auto-snapshot first — the manual step in [[runbooks/update-hermes-safely]] step 1 is currently the only safety net.
|
||||
|
||||
## Relevant runbooks
|
||||
|
||||
@@ -3,8 +3,8 @@ title: Credentials Map
|
||||
type: infrastructure
|
||||
status: active
|
||||
created: 2026-07-22
|
||||
updated: 2026-07-22
|
||||
verified_on: 2026-07-22
|
||||
updated: 2026-10-20
|
||||
verified_on: 2026-10-20
|
||||
confidence: medium
|
||||
tags: [credentials, security, infrastructure]
|
||||
sources: []
|
||||
@@ -32,6 +32,19 @@ Document where credentials are stored and what service they belong to.
|
||||
| Huawei Cloud | Terraform state / config | Unverified | |
|
||||
| GitHub | Hermes config / gh CLI | `~/.config/gh/` or `~/.hermes/` | Unverified |
|
||||
|
||||
> **Re-verified 2026-10-20 — two corrections to the table above.**
|
||||
> 1. **Email credentials live in `~/.hermes/.env`, not `config.yaml`.** `config.yaml` has **no**
|
||||
> `imap`/`smtp`/`email` keys; the live variables are `EMAIL_ADDRESS`, `EMAIL_IMAP_HOST`,
|
||||
> `EMAIL_SMTP_HOST`, `EMAIL_ALLOWED_USERS`, `EMAIL_HOME_ADDRESS`, `EMAIL_ALLOW_ALL_USERS`
|
||||
> and friends in `~/.hermes/.env` (mode `0600`). The `config.yaml` row is wrong — point at the `.env`.
|
||||
> 2. **The `tools:` block in `config.yaml` contains only `tool_search`.** There are no `gmail`,
|
||||
> `discord`, `mattermost` or `email` tool sections there. Discord and Telegram appear as
|
||||
> **top-level** `discord:` / `telegram:` blocks, and Mattermost is a **plugin**
|
||||
> (`platforms/mattermost`), not a `tools:` entry. So the "Hermes config" location column is right
|
||||
> for those, but the implication that they are `tools:` sections is not.
|
||||
> No `connectors:` block is configured in `config.yaml` at all.
|
||||
> `~/.hermes/auth.json` also exists and holds OAuth tokens — treat as a credential store.
|
||||
|
||||
## Rules
|
||||
- Credentials never written to this wiki
|
||||
- API vault is first-stop for any key lookup
|
||||
|
||||
@@ -3,8 +3,8 @@ title: Domains and Tunnels
|
||||
type: infrastructure
|
||||
status: active
|
||||
created: 2026-07-22
|
||||
updated: 2026-07-22
|
||||
verified_on: 2026-07-22
|
||||
updated: 2026-10-20
|
||||
verified_on: 2026-10-20
|
||||
confidence: high
|
||||
tags: [infrastructure, network, cloudflare]
|
||||
sources: [raw/configs/hermes-config-sanitized.txt]
|
||||
@@ -31,7 +31,30 @@ Where `martinwa.org` subdomains point, and how they reach internal services.
|
||||
| `omniroute.martinwa.org` | `http://omniroute.kangaroo-eel.ts.net:20128` | Public front for [[systems/omniroute]] |
|
||||
| `nanobot.martinwa.org` / `nano-ssh.martinwa.org` | `100.122.189.81` (ct333 "clawtest") | See [[comparisons/hermes-vs-nanobot]] |
|
||||
|
||||
`mcp-portal.martinwa.org` is not present in the ct207 ingress list captured during this audit — it may be served by a different tunnel/host, or the ingress list may have moved since. **Unknown**, flagged for follow-up rather than guessed.
|
||||
`mcp-portal.martinwa.org` is **still not present** in the ct207 ingress list — re-read live from
|
||||
`/etc/cloudflared/config.yml` on ct207 on **2026-10-20**. It may be served by a different
|
||||
tunnel/host, or the ingress list may have moved since. **Still unknown**, still flagged for
|
||||
follow-up rather than guessed.
|
||||
|
||||
### Ingress changes found 2026-10-20 (full live re-read of ct207 `config.yml`)
|
||||
|
||||
The hostname list had drifted from the 2026-07-22 capture. Verified additions and corrections:
|
||||
|
||||
| Hostname | Live target | Note |
|
||||
|---|---|---|
|
||||
| `hermes-chat.martinwa.org` | `http://100.118.5.51:8787` | **new** — WebUI |
|
||||
| `tg.hermes.martinwa.org` | `http://100.118.5.51:19119` | **new** — Telegram bot webhook |
|
||||
| `openwebui.martinwa.org` | `http://100.69.230.13:4000` | **new** — Open WebUI |
|
||||
| `news.martinwa.org` | `http://docker.kangaroo-eel.ts.net:8300` | **new** — WorldMonitor |
|
||||
| `ssh-pve.martinwa.org` | `http://100.96.100.82:7681` | **new** — PVE noVNC |
|
||||
| `nextcloud.martinwa.org` | `https://100.90.102.19:443` | target corrected (was `100.96.150.69`) |
|
||||
| `readlater.martinwa.org` | `http://100.96.150.69:6123` | confirmed |
|
||||
| `velvet.martinwa.org` | `http://127.0.0.1:8888` | confirmed |
|
||||
| `runtipi.martinwa.org` | `http://100.96.244.39:80` | confirmed |
|
||||
| `homar.martinwa.org` | `http://100.96.244.39:8102` | confirmed — this is **Homarr**, the live dashboard (see [[systems/homepage-dashboard]]) |
|
||||
|
||||
The catch-all remains `service: http_status:404`. The ct207 `config.yml` still carries ~25 dated
|
||||
`config.yml.bak*` files, newest `config.yml.bak.1781809151`.
|
||||
|
||||
## Full ct207 ingress list (context, not all Hermes-related)
|
||||
The tunnel also fronts: `pve.martinwa.org` (Proxmox UI), `docker.martinwa.org` (Portainer), `runtipi.martinwa.org`, `homar.martinwa.org`, `nextcloud.martinwa.org`, `readlater.martinwa.org`, `velvet.martinwa.org`, `overtchat.martinwa.org`, `freellmapi.martinwa.org`, `omnideb.martinwa.org`, `newstarter.martinwa.org`, and SSH endpoints for debianvm/pve/webserver. These belong to the wider homelab, not Hermes specifically — recorded here only so an ingress diff is possible later.
|
||||
|
||||
Reference in New Issue
Block a user