-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Add chat-ui
and chat-ui-db
docker images
#613
Conversation
I think we can revert this and keep it as today. |
Question, isn't it better to have a single container for each process (and use with Docker compose)? |
I replaced this setup with two images, one |
8751c6b changes it back! |
I've updated the dockerfile and associated workflow in 6a85c2d so that we now build two separate images.
|
Dockerfile.local
image to buildchat-ui
and chat-ui-db
docker images
cc @XciD I think we talked at some point about making an image that wouldn't need the |
Merging this now, it doesn't change anything in code or docs, it just adds extra stuff. I want to see if it builds and deploys correctly to ghcr. Once it works I'll update the docs. |
* Add a `Dockerfile.local` image to build * Add a build & publish workflow * fix workflow * Add support for local mongoDB * Fix problem with POST requests * use slim image * Set mistral to be the default model in .env * Fix entrypoint * Revert change regarding config folder * replace env variable by build arg for DB and update work * old mention of `conf` folder in readme * env to .env * Revert readme changes * lint
The goal is to end up with a docker image that we can build in CI, that will not contain any secrets. Then users will be able to just
docker run chat-ui:latest
and mount their.env.local
either as a bind volume or as an env variable.To-do
Update the readme with steps to run chat-ui using docker only(I will do this in a later PR once i'm sure everything works)Testing locally
Building the image
(this step won't be needed in the future, as we will build the image in our CI pipeline)
Building the image without db (
chat-ui
):Building the image with db (
chat-ui-db
):The
chat-ui-db
image will override anyMONGODB_URL
set and will use the included DB instead.Running the image
Simplest possible run, DB included & default config:
Custom config
You can specify a DOTENV_LOCAL by passing an env variable at
docker run
time:Or you can use a bind volume pointing to
.env.local
directly