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

Document Firecrawl backend selection

Browse Source
This commit is contained in:
root 2026-05-27 18:52:39 +00:00
parent 08f32a79e8
commit 4249b17afc
2 changed files with 3 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
docs/hermes-operations.md
View File

@ -18,6 +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
- 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

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

@ -232,6 +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.
- [ ] SearXNG self-hosted option
- [ ] Configure browser automation only if needed and keep it private/safe:
- [ ] local Chromium/Camofox, or