No way to choose model in Ollama
Closed this issue · 6 comments
Hello @SoiledBrush! Integration with Ollama is an early preview. Nonetheless, it should fetch the tags of models available locally.
I have just tested it on a fresh Grimoire + Ollama installation, and it works just fine. Please keep in mind, that you need to press the TEST button to make a first call to Ollama's API.
![Screenshot 2023-12-10 at 12 41 01](https://private-user-images.githubusercontent.com/43510122/289355823-fec7c842-189c-4499-8409-24189b392489.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTkzOTk3MjgsIm5iZiI6MTcxOTM5OTQyOCwicGF0aCI6Ii80MzUxMDEyMi8yODkzNTU4MjMtZmVjN2M4NDItMTg5Yy00NDk5LTg0MDktMjQxODliMzkyNDg5LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA2MjYlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNjI2VDEwNTcwOFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTRiNTEzMmVjMjVhNjhjYTJjZWFlNjE2NWRlNDhjYjkyNGY0NmRiNjFjNThlNDQ1ZWI3NGM5MGQ2NzQyMWNiMTkmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.V-8Ivvt4bW-VE2oAq5fQRuSx8QSmbz-wgMPr1YqE7uE)
Ok, test buttons works if I start grimoire on the local machine. But doesn't work if I run it in on my "homelab".
Maybe it has something to do with the fact that I changed ORIGIN=http://localhost:5173 to http://10.0.0.254:5173 to avoid "cross-site form submissions forbidden" error.
You probably should configure Ollama to accept incoming request from Grimoire's origin. Please refer to this document for more information: https://github.com/jmorganca/ollama/blob/main/docs/faq.md#how-can-i-expose-ollama-on-my-network
cat /etc/systemd/system/ollama.service.d/environment.conf
[Service]
Environment="OLLAMA_HOST=0.0.0.0:11434"
I already have that set up.
Ok, I see. I don't know what's the exact origin of the request that comes from Grimoire. The call to Ollama API is made on the client-side, so you can check the response for it in the Network tab in your browser.
It should be now fully resolved with the fixes/improvements made for #71.