-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Switch to webUI #48
Comments
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? |
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. |
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? |
I asked about it here mudler/LocalAI#2156 (comment) |
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 #31 and do away with editing the
modules.yaml
file directly, solving issues like nextcloud/all-in-one#5602The text was updated successfully, but these errors were encountered: