bytelyst/bytelyst-devops-tools
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Mark Firecrawl as locally configured

Browse Source
This commit is contained in:
root 2026-05-27 18:57:44 +00:00
parent 70d96d7684
commit d1f234fc01
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/hermes-operations.md
View File

@ -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

4
docs/hermes-setup-upgrade-roadmap.md
View File

@ -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