Replies: 2 comments
-
|
I suppose this may also be a good example of how to setup literally every one of the components locally for a perpetually running local development memory system via docker-compose (though at this point maybe I should just throw it into a kube cluster via a helm chart I suppose...) |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
When updated to use the root postgres credentials it initialized the database without issues and started using it. It seems to try to run the init via the public/default database which maybe why it fails with the designated account? |
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.
Uh oh!
There was an error while loading. Please reload this page.
-
I've created a local dockerfile for building the application with the UI flag then updated a docker compose to launch it in UI mode along with external services for all the state components (postgres, redis, qdrant). Most everything comes online but I run into 2 issues:
The UI seems to work, allows for MCP server configuration and session creation/deletion. But does not allow for anything to be entered into the chat window.I was missing port 3001 for the websocket connection in my docker-compose.Postgres initialization fails no matter what I throw at it to try to get it working. I get some confusing log output like the following:
My
docker-compose.ymlif that helps at all:The docker image itself (mostly cloned from the official one but using git to pull and build the project):
Beta Was this translation helpful? Give feedback.
All reactions