Docker-compose.yml access to custom librechat.yaml overwritten in upgrade

[hopeseekr]

What happened?

The Problem

Upon doing an upgrade of LibreChat, I lost access to all custom LLM configs (DeepSeek, Perplexity, etc.).

The reason wasn't immediately clear. I thought at first it was the UI refresh, as that seemed most logical.

Upon further investigation, it seems that my docker-compose.yml file was overwritten, leading tot he loss of the mapping to librechat.yaml.

The Solution

1. Copy the default /app/librechat.yaml to librechat.yaml in the root directory.
2. Add the following to docker-compose.yml:

    volumes:
      - type: bind
        source: ./librechat.yaml
        target: /app/librechat.yaml

Now, when the systme is upgraded, the docker-compose.yml will still have proper references for loading librechat.yaml, and the user's custom settings won't be lost.

[danny-avila]

The docker-compose.yml file clearly states:

LibreChat/docker-compose.yml

Lines 1 to 2 in 8fb6c38

	# Do not edit this file directly. Use a ‘docker-compose.override.yaml’ file if you can.
	# Refer to `docker-compose.override.yaml.example’ for some sample configurations.

When adding custom endpoints, our documentation states to make use of the docker-compose.override.yaml file as well:

https://www.librechat.ai/docs/quick_start/custom_endpoints#step-1-create-or-edit-a-docker-override-file