Why does LocalAGI change LocalAI port to 8081? #5919
Unanswered
gitwittidbit
asked this question in
Q&A
Replies: 1 comment
-
The main idea is that LocalAGI would have been the "front-end" while LocalAI would simply be sit as a backend for the stack. Of course the docker-compose is meant also an example, so you can change as much as needed. I also don't have a strong opinion on this, so I'd be ok to swapping these back |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Just wondering...
LocalAI used to use port 8080. Now LocalAGI comes along and uses 8080 (externally while internally using 3000) so that LocalAI has to move to 8081. Why not have LocalAI keep 8080 and have LocalAGI use 8081 (or 3000)?
Because now it breaks all setups that expect LocalAI on port 8080. I mean, it's not a big thing to change the setups. But what is the idea behind that port swap?
Beta Was this translation helpful? Give feedback.
All reactions