Andreas/LibreChat
1
0
Fork 0
mirror of https://github.com/danny-avila/LibreChat.git synced 2025-12-29 22:58:51 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions 3

🎨 fix: Optimize StableDiffusion API Tool and Fix for Assistants Usage (#2253)

Browse source 
* chore: update docs

* fix(StableDiffusion): optimize API responses and file handling, return expected metadata for Assistants endpoint
This commit is contained in:
Danny Avila 2024-03-30 20:09:59 -04:00 • committed by GitHub
parent 56ea0f9ae7
commit bb8a40dd98
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
9 changed files with 113 additions and 52 deletions
Download patch file Download diff file Expand all files Collapse all files

14
docs/install/installation/docker_compose_install.md
View file

@ -51,7 +51,12 @@ Once you have completed all the setup, you can start the LibreChat application b
That's it! If you need more detailed information on configuring your compose file, see my notes below.
## Updating LibreChat
The following commands will fetch the latest code of LibreChat and build a new docker image.
As of v0.7.0+, Docker installations transitioned from building images locally to using prebuilt images [hosted on Github Container registry](https://github.com/danny-avila?tab=packages&repo_name=LibreChat).
You can still build the image locally, as shown in the commented commands below. More info on building the image locally in the [Docker Compose Override Section](../configuration/docker_override.md).
The following commands will fetch the latest LibreChat project changes, including any necessary changes to the docker compose files, as well as the latest prebuilt images.
```bash
# Stop the running container(s)
@ -63,13 +68,16 @@ git pull
# Pull the latest LibreChat image (default setup)
docker compose pull
# If building the LibreChat image Locally, build without cache (legacy setup)
# docker compose build --no-cache
# Start LibreChat
docker compose up
```
If you're having issues running the above commands, you can try a comprehensive approach:
If you're having issues running the above commands, you can try a comprehensive approach instead:
Prefix commands with `sudo` according to your environment permissions.
Note: you may need to prefix commands with `sudo` according to your environment permissions.
```bash
# Stop the container (if running)