I am using OpenAIlike endpoint. This endpoint is basically a local connection to GitHub Copilot, which gives access to GPT 4 models and Claude Sonnet. I am not sure what the problem is, any suggestions?
changed category to “bolt.diy troubleshooting”
Can you share a view screenshots of your bolt.diy settings / browser and also give more details what this service is you connect to?
As far as I see your local git service does not provide a model list. Also you should try to request your service without bolt, to make sure it is working (curl against the endpoints)
it does seem that the .env file is not being loaded properly into the container. the variables i use, which is OPENAI_LIKE_API_BASE_URL and OPENAI_LIKE_API_KEY are missing. But this doesn’t make sense, because they are set correctly inside the .env
Also bolt is able successfully connect to my local server and get the models list as u see in the image below. This means my models endpoint is working fine.
Unfortunately this is not possible at the moment. @ColeMedin is on it to fix some stuff and change regulations. But for now you need to wait I guess 15 hours / beeing a member a bit longer, to post more stuff.
Thanks for the suggestion to use host.docker.internal, it worked perfectly. However, I needed to make additional modifications to the docker-compose.yml file to get everything working as expected:
Issue with .env Changes:
I noticed that when making changes to the .env file, the Docker container detects those changes and restarts itself automatically. However, it doesn’t actually apply the updated environment variables unless the project is rebuilt. To resolve this, I manually rebuilt the containers whenever I updated the .env file:
Default docker-compose.yml Configuration:
The default docker-compose.yml file was configured to use env_file: ".env.local". Since the repository doesn’t include a .env.local file and only provides a .env file, I updated it to reference .env instead:
Explicit Network Declaration:
I added a custom network to better organize the services. This wasn’t strictly necessary, but it helped ensure all containers are on the same network for consistency:
Now it works finally. But since i did not use the app yet, its giving me this terminal error, is this an expected behavior or is there something wrong again with my installation?