localai-webui example missing .env file

[jamesbraza]

Going to examples/localai-webui and running it per the examples/localai-webui/README.md:

> docker-compose up --pull always
Failed to load /Users/user/code/repo/localai/examples/localai-webui/.env: open /Users/user/code/repo/localai/examples/localai-webui/.env: no such file or directory

I think a placeholder .env file needs to be added to this folder.

[jamesbraza]

The examples/slack-bot/ has a .env.example that its README instructs to cp to a .env file. I think something like this should be added for localai-webui

[localai-bot]

⚠️⚠️⚠️⚠️⚠️

Hi! I'm a bot running with LocalAI ( a crazy experiment of @mudler ) - please beware that I might hallucinate sometimes!

but.... I can also be funny or helpful 😸 and I can provide generally speaking good tips or places where to look after in the documentation or in the code based on what you wrote in the issue.

Don't engage in conversation with me,
I don't support (yet) replying!

⚠️⚠️⚠️⚠️⚠️

Yes, that is correct. The docker-compose.yaml file in the examples/localai-webui directory assumes that there is a .env file present with certain environment variables defined. You can create a new .env file and set the appropriate variables for your setup. Here's an example of what the .env file might look like:

# Set number of threads.
THREADS=2
# Specify a different bind address (defaults to ":8080")
ADDRESS=127.0.0.1:8080

Make sure to update the ADDRESS variable with an appropriate IP address or FQDN for your setup. Once you've created the .env file, you can run docker-compose up --pull always again and it should work as expected.

Sources:

• https://github.com/go-skynet/LocalAI/tree/master/examples/localai-webui/README.md
• https://localai.io/howtos/easy-setup-docker-gpu/index.html
• https://github.com/go-skynet/LocalAI/tree/master/examples/chatbot-ui/README.md
• https://localai.io/howtos/easy-setup-full/index.html

[jamesbraza]

Thanks @localai-bot. I think the repo should have an .env file already present, users shouldn't have to create one after the code crashes