Open Sir-Photch opened 9 months ago
Thanks for the issue!
So, I'm looking into implementing this (if that's OK). My plan was to reuse the OLLAMA_HOST
variable but model it after DOCKER_HOST
:
IP:PORT
and IP
.tcp://IP:PORT
.unix:///path/to/socket
.Thoughts?
(eventually I'd like to add systemd socket activation)
@Stebalien how are you getting on with this, I'm also interested and potentially can justify putting some time towards it if you need some help?
I was waiting for feedback but missed the :+1:. I have no plans to tackle it immediately (I'll wait till I get a free weekend) so go for it.
This'd be nice to have. I was thinking it'd be useful in combination with some sort of listener from systemd to start the server on-demand.
It would be helpful for security concerns on multi-user machines.
For usecases when there is a reverse-proxy in front of ollama, it would make sense to enable listening on a unix socket instead of a port, that is
/path/to.socket
. This would reduce unnecessary TCP/IP-overhead between reverse proxy and ollama, as well as enable security configurations with unix file permissions.