Why is ollama tied to the kotemon?

[r0kk]

Hi @taprosoft , I would be happy to know, what is the reasoning behind tying ollama to the docker build? To me it looks like a big dependency and is moving koteamon away where each party chooses its own model providers.

Why I am asking is:

• It is a bit of a pain to maintain a fork, so it would be easier to leave it with as little dependencies as needed.
• Whoever is keeping track with new releases, now has one new big dependency.

Thank you.

I am talking about the following changes:

• Dockerfile
• Launch.sh

[taprosoft]

Hi @r0kk, thanks for your interest. I understand your concern regarding new dependency, especially when it is large and not beneficial to every users. For this Ollama update, actually we leave the Ollama-Docker integration optional for developer, and still recommend the full target as default use.

To use the Dockerfile with full build target instead of the final target ollama, use docker build --target full.
For the new launch script, if you are comfortable by modifying the entrypoint of the Docker build, just use python app.py as previous version. Or, the new launch script still work if ollama does not exists or returns errors, so no change in the startup process if you don't want to install Ollama.

Overall, we will keep a careful approach regarding new external dependency. Also, we will provide these extensions as optional just like the new build target or the launch script so it is mostly backward compatible.

[r0kk]

Hi @taprosoft, that is great. Thank you for your kind feedback. I somehow missed the full target. Apologies.