search

szaimen / aio-local-ai

GNU Affero General Public License v3.0
3 stars 2 forks source link

Switch to webUI #48

Open ShapeShifter499 opened 1 week ago

ShapeShifter499 commented 1 week ago

Why don't we expose the LocalAI web interface like we do with the mastercontainer? So that people can download and configure models without needing to worry about editing the modules.yaml file. Allow it to be accessible localhost and people can tunnel over ssh remotely.

This would possibly eliminate the concerns of https://github.com/szaimen/aio-local-ai/issues/31 and do away with editing the modules.yaml file directly, solving issues like https://github.com/nextcloud/all-in-one/issues/5602

szaimen commented 5 days ago

Hi, thanks for your request! Do you know if the web interface of local-ai can be protected with a password for example? I fear this would be needed before we can expose it. Maybe if not possible, there is a feature request on local-ai that can be tracked?

ShapeShifter499 commented 3 days ago

Do you know if the web interface of local-ai can be protected with a password for example?

I do not, I can't find any mention in their user guide either. There is a mention of a authorization token but I am guessing that's for connecting other applications.

I was kind of assuming that one wouldn't directly expose the UI to the internet and instead put it behind some oath system or even limit it to just localhost and tunneling to it via ssh.

szaimen commented 3 days ago

To do this properly there needs to be some protection for the web interface e.g. via password or token. So peobably a feature request on local-ai needs to be created?

ShapeShifter499 commented 3 days ago

I asked about it here https://github.com/mudler/LocalAI/issues/2156#issuecomment-2493418192