A start-to-finish macOS guide, and a corpus default that works off a server - #336
Merged
Merged
Conversation
… works off a server The macOS path was accurate in the README but not a walkthrough, and the first run failed for a reason nothing explained: the corpus defaults to /data/knowledge-base, a server convention that does not exist on a laptop and cannot be created without root. When that path is absent the default is now a directory beside the code, seeded on first start, so `pnpm start` works from a fresh clone. Deployments set KB_ROOT and are unaffected. docs/MACOS.md is the whole path in the order worth doing it: run it first, add GUFI once it works, add a model last. It says what works in each of the three states, since a Mac user without the vector extensions still gets filename and full-text search and only loses the semantic blend, and it answers the failures that actually happen, which are Apple clang instead of Homebrew LLVM, and the llama.cpp build inside sqlite-lembed. GUFI itself is installed from GUFI: the guide points at the project and the Studio finds gufi_query on PATH or under /opt/gufi/bin.
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
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.
The first run failed for an unexplained reason.
KB_ROOTdefaults to/data/knowledge-base, a server convention that does not exist on a laptop and cannot be created without root. When that path is absent the default is nowknowledge-base/beside the code, seeded on first start, sopnpm startworks from a fresh clone. Deployments setKB_ROOTexplicitly and are unaffected.docs/MACOS.mdis the path in the order worth doing it: run it first, add GUFI once it works, add a model last. It includes a table of what works in each of the three states, because a Mac user who builds withGUFI_AI=0still gets filename and full-text search over extracted document text and only loses the semantic blend, which is a much better story than "unsupported". Troubleshooting covers the failures that actually happen: Apple clang instead of Homebrew LLVM, and the llama.cpp build inside sqlite-lembed.GUFI binaries are not shipped here and should not be: the guide points at the GUFI project for installation, notes that a site package works, and documents that the Studio finds
gufi_queryonPATHor under/opt/gufi/bin.indexer/setup_gufi.shremains available for building from source.174 server tests and 9 web tests pass, and the macOS CI job covers this on a real runner.