docs(guides): local Ollama setup (salvage #5842)#20426
Merged
Merged
Conversation
Step-by-step guide covering Ollama installation, model selection, Hermes configuration, speed optimization, and optional gateway bot setup — all running on local hardware with zero API cost. Includes hardware requirements, model comparison table with tool-call support status, context window tuning, GPU offloading tips, fallback provider setup, troubleshooting, and cost comparison.
alt-glitch
added
type/docs
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a 317-line guide for running Hermes entirely locally with Ollama — hardware requirements, Ollama install, Hermes custom_providers wiring, model picking, gateway/Telegram deployment.
Changes:
website/docs/guides/local-ollama-setup.md(+317, new file)scripts/release.py— AUTHOR_MAP entry for binhnt92Dropped from the original PR:
gateway/platforms/slack.py+gateway/platforms/signal.pylock-release fix — current main already handles this viatry/finallyinconnect()calling_release_platform_lock()when_running is False(slack.py:680, signal.py:287). The PR's fix is a different shape of the same solution against a stale tree.Closes #5842 via salvage.
Original PR by @binhnt92 — authorship preserved.