nextcloud / nextcloud/context_chat_backend
[feat]: build llama-cpp-python instead of using the whl
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 27
- Forks
- 24
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 6
Description
Describe the feature you'd like to request
Instead of using the whl file from https://github.com/abetlen/llama-cpp-python/releases, build the package in the docker container. Newer versions of llama-cpp-python haven't had pre-built releases recently which would make building the only way to have them officially.
This will also solve #126 and https://github.com/nextcloud/context_chat_backend/issues/178#issuecomment-2883603247 (using app_api's env declaration for CMAKE_ARGS).
Some related links:
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the llama-cpp-python docker/cuda_simple/Dockerfile linked in the issue with this repository's container build configuration. Check how app_api environment declarations can provide CMAKE_ARGS, and use the newer llama-cpp-python build path as the completion target, including the referenced GGML_CPU_ALL_VARIANTS option where appropriate.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cmake, docker, python
- Domain
- build-system, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100