nextcloud / nextcloud/context_chat_backend
[feat] [doc improvement]: Where does context chat backend get its compute?
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
I finally got context chat working, and it has tremendous potential. I am running our server on a digitalocean droplet, and do our computing on a separate ollama server.
I looked at the configuration file /nc_app_context_chat_backend_data/config.yaml, but I don't have the skills to understand where the computing is happening. If I had to guess, I would guess it's all happening locally. For sure any request takes a very long time (up to 60 minutes) and doesn't seem to register on the GPU server. I can't tell, and the documentation doesn't help too much.
Describe the solution you'd like
- Please take a moment to explain to me where models are being computed
- If it is as I suspect and everything happens local, then a small section in the documentation that explains this would be useful - I'm happy to write this and submit a PR
- Is it possible to use other computing resources? If so, how?
- If yes to above, then this should also be documented - again happy to write this and submit a PR
Describe alternatives you've considered
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 with /nc_app_context_chat_backend_data/config.yaml and the existing documentation; trace which configured service receives model requests. Document where computation occurs, how to use a separate Ollama server if supported, and clarify the expected deployment behavior so users can verify it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ollama, python
- Domain
- backend, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100