From d1f234fc0179d6ec87bd5de8c4d072aa86d7883b Mon Sep 17 00:00:00 2001 From: root Date: Wed, 27 May 2026 18:57:44 +0000 Subject: [PATCH] Mark Firecrawl as locally configured --- docs/hermes-operations.md | 2 +- docs/hermes-setup-upgrade-roadmap.md | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/hermes-operations.md b/docs/hermes-operations.md index 19f0bb3..119f890 100644 --- a/docs/hermes-operations.md +++ b/docs/hermes-operations.md @@ -18,7 +18,7 @@ Observed on 2026-05-27: - `qwen2.5-coder:7b` - `llama3.1:8b` - `llama3.2-vision` -- Web backend target: Firecrawl, pending API key or self-hosted Firecrawl endpoint +- Web backend target: Firecrawl, configured locally on root and Uma with a private API key - Backup cron: `Sync Hermes persistent-data backup to GitHub`, every 30 minutes, local delivery - Systemd persistent backup timers: `hermes-root-backup.timer` and `uma-hermes-backup.timer`, every 10 minutes - Watchdog cron: `ByteLyst Hermes gateway/backup/disk watchdog`, every 15 minutes, Telegram delivery on failure only diff --git a/docs/hermes-setup-upgrade-roadmap.md b/docs/hermes-setup-upgrade-roadmap.md index 9fbc0c1..a7d9e39 100644 --- a/docs/hermes-setup-upgrade-roadmap.md +++ b/docs/hermes-setup-upgrade-roadmap.md @@ -232,8 +232,8 @@ A healthy ByteLyst Hermes setup should be: - [ ] Exa - [ ] Tavily - [ ] Firecrawl - - vijay: Firecrawl is selected in both Hermes configs; waiting on API key or a self-hosted endpoint. - - bheem: same pending auth state applies to Uma. + - vijay: Firecrawl is selected in both Hermes configs and the local API key is now loaded for root. + - bheem: same local Firecrawl configuration is loaded for Uma. - [ ] SearXNG self-hosted option - [ ] Configure browser automation only if needed and keep it private/safe: - [ ] local Chromium/Camofox, or