You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/features/manage_your_database.md
+27-33Lines changed: 27 additions & 33 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,9 +18,9 @@ To enhance the security of your data, external ports for MongoDB are not exposed
18
18
19
19
Mongo Express allows you to interact with your MongoDB database through your browser. To set it up, perform the following steps:
20
20
21
-
1. Create a new file named `docker-compose.override.yml` in the same directory as your main `docker-compose.yml` file for LibreChat.
22
-
23
-
2. Copy the following contents into the `docker-compose.override.yml` file:
21
+
### Setting up Mongo Express service
22
+
- Create a new file named `docker-compose.override.yml` in the same directory as your main `docker-compose.yml` file for LibreChat.
23
+
- Copy the following contents into the `docker-compose.override.yml` file:
24
24
25
25
```yaml
26
26
version: '3.4'
@@ -39,55 +39,49 @@ services:
39
39
- mongodb
40
40
restart: always
41
41
```
42
-
43
-
3. **Security Notice:**
44
-
42
+
### Security Notice
45
43
- Before using this configuration, replace `admin` and `password` with a unique username and password for accessing Mongo Express. These credentials should be strong and not easily guessable to prevent unauthorized access.
46
44
- Optional: You can also add native authentication to your database. See the [`docker-compose.override` guide](../install/configuration/docker_override.md#mongodb-authentication) for instructions on how to do so.
47
-
- If utilizing authentication, ensure the admin user has the "clusterAdmin" and "readAnyDatabase" permissions. These steps are detailed in the [docker-compose.override guide](../install/configuration/docker_override.md#step-1-creating-an-admin-user).
48
-
- After following the guide to authenticate MongoDB, you will need these variables under the environment section for mongo-express:
49
-
50
-
```yaml
51
-
environment:
52
-
ME_CONFIG_MONGODB_SERVER: mongodb
53
-
ME_CONFIG_BASICAUTH_USERNAME: admin
54
-
ME_CONFIG_BASICAUTH_PASSWORD: password
55
-
# database authentication variables, using example credentials from guide
4. Save the `docker-compose.override.yml` file and run the following command from the directory where your `docker-compose.yml` file is located to start Mongo-Express along with your other Docker services:
45
+
- If utilizing authentication, ensure the admin user has the "clusterAdmin" and "readAnyDatabase" permissions. These steps are detailed in the [docker-compose.override guide](../install/configuration/docker_override.md#step-1-creating-an-admin-user).
46
+
- After following the guide to authenticate MongoDB, you will need these variables under the environment section for mongo-express:
47
+
48
+
```yaml
49
+
environment:
50
+
ME_CONFIG_MONGODB_SERVER: mongodb
51
+
ME_CONFIG_BASICAUTH_USERNAME: admin
52
+
ME_CONFIG_BASICAUTH_PASSWORD: password
53
+
# database authentication variables, using example credentials from guide
- Save the `docker-compose.override.yml` file and run the following command from the directory where your `docker-compose.yml` file is located to start Mongo-Express along with your other Docker services:
62
61
63
62
```
64
63
docker-compose up -d
65
64
```
66
-
67
65
This command will merge the `docker-compose.override.yml` with your `docker-compose.yml` and apply the configuration.
68
66
69
-
5. Once Mongo-Express is up and running, access it by navigating to `http://localhost:8081` in your web browser. You'll need to enter the username and password you specified for `ME_CONFIG_BASICAUTH_USERNAME` and `ME_CONFIG_BASICAUTH_PASSWORD`.
67
+
-Once Mongo-Express is up and running, access it by navigating to `http://localhost:8081` in your web browser. You'll need to enter the username and password you specified for `ME_CONFIG_BASICAUTH_USERNAME` and `ME_CONFIG_BASICAUTH_PASSWORD`.
70
68
71
69
---
72
70
73
71
## Removing Mongo Express
74
-
75
72
If you wish to remove Mongo-Express from your Docker environment, follow these straightforward steps:
73
+
- Navigate to the directory containing your `docker-compose.yml` and `docker-compose.override.yml` files.
76
74
77
-
1. Navigate to the directory containing your `docker-compose.yml` and `docker-compose.override.yml` files.
78
-
79
-
2. Bring down the current Docker environment, which will stop and remove all running containers defined in the `docker-compose.yml` and `docker-compose.override.yml` files. Use the following command:
80
-
81
-
```
75
+
- Bring down the current Docker environment, which will stop and remove all running containers defined in the `docker-compose.yml` and `docker-compose.override.yml` files. Use the following command:
76
+
```sh
82
77
docker-compose down
83
78
```
84
79
85
-
3. Now you can either rename or delete the `docker-compose.override.yml` file, which contains the Mongo Express configuration.
86
-
87
-
4. Finally, bring your Docker environment back up, which will now exclude Mongo Express:
80
+
- Now you can either rename or delete the `docker-compose.override.yml` file, which contains the Mongo Express configuration.
88
81
82
+
- Finally, bring your Docker environment back up, which will now exclude Mongo Express:
89
83
```
90
84
docker-compose up -d
91
85
```
92
86
93
-
By following these steps, you will have successfully removed Mongo Express from your Docker environment. If you want to reinstate Mongo Express at a later time, you can either rename the backup file back to `docker-compose.override.yml` or recreate the original `docker-compose.override.yml` file with the Mongo Express configuration.
87
+
> By following these steps, you will have successfully removed Mongo Express from your Docker environment. If you want to reinstate Mongo Express at a later time, you can either rename the backup file back to `docker-compose.override.yml` or recreate the original `docker-compose.override.yml` file with the Mongo Express configuration.
Copy file name to clipboardExpand all lines: docs/install/configuration/docker_override.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -100,6 +100,7 @@ Use of the `docker-compose.override.yml` file allows us to enable explicit authe
100
100
- While the steps outlined may also be applicable to Docker Desktop environments, or with non-Docker, local MongoDB, or other container setups, details specific to those scenarios are not provided.
101
101
102
102
**There are 3 basic steps:**
103
+
103
104
- Create an admin user within your mongodb container
104
105
- Enable authentication and create a "readWrite" user for "LibreChat"
-`DALLE_API_KEY`: This environment variable is intended for storing the OpenAI API key that grants access to both DALL-E 2 and DALL-E 3 services. Typically, this key should be kept private. If you are distributing a plugin or software that integrates with DALL-E, you may choose to leave this commented out, requiring the end user to input their own API key. If you have a shared API key you want to distribute with your software (not recommended for security reasons), you can uncomment this and provide the key.
423
423
424
424
```bash
425
-
#DALLE_API_KEY=
425
+
DALLE_API_KEY=
426
426
```
427
427
428
428
-`DALLE3_API_KEY` and `DALLE2_API_KEY`: These are similar to the above but are specific to each version of DALL-E. They allow for separate keys for DALL-E 2 and DALL-E 3, providing flexibility if you have different access credentials or subscription levels for each service.
429
429
430
430
```bash
431
-
#DALLE3_API_KEY=
432
-
#DALLE2_API_KEY=
431
+
DALLE3_API_KEY=
432
+
DALLE2_API_KEY=
433
433
```
434
434
435
435
**System Prompts:**
436
436
-`DALLE3_SYSTEM_PROMPT` and `DALLE2_SYSTEM_PROMPT`: These variables allow users to set system prompts that can preconfigure or guide the image generation process for DALL-E 3 and DALL-E 2, respectively. Use these to set default prompts or special instructions that affect how the AI interprets the user's input prompts.
437
437
438
438
```bash
439
-
#DALLE3_SYSTEM_PROMPT="Your DALL-E-3 System Prompt here"
440
-
#DALLE2_SYSTEM_PROMPT="Your DALL-E-2 System Prompt here"
439
+
DALLE3_SYSTEM_PROMPT="Your DALL-E-3 System Prompt here"
440
+
DALLE2_SYSTEM_PROMPT="Your DALL-E-2 System Prompt here"
441
441
```
442
442
443
443
**Reverse Proxy Settings:**
444
444
-`DALLE_REVERSE_PROXY`: This setting enables the specification of a reverse proxy for DALL-E API requests. This can be useful for routing traffic through a specific server, potentially for purposes like caching, logging, or adding additional layers of security. Ensure that the URL follows the required pattern and is appropriately configured to handle DALL-E requests.
445
445
446
446
```bash
447
-
#DALLE_REVERSE_PROXY=
447
+
DALLE_REVERSE_PROXY=
448
448
```
449
449
450
450
**Base URLs:**
451
451
-`DALLE3_BASEURL` and `DALLE2_BASEURL`: These variables define the base URLs for DALL-E 3 and DALL-E 2 API endpoints, respectively. These might need to be set if you are using a custom proxy or a specific regional endpoint provided by OpenAI.
452
452
453
453
```bash
454
-
#DALLE3_BASEURL=
455
-
#DALLE2_BASEURL=
454
+
DALLE3_BASEURL=
455
+
DALLE2_BASEURL=
456
456
```
457
457
458
458
**Azure OpenAI Integration (Optional):**
459
459
-`DALLE3_AZURE_API_VERSION` and `DALLE2_AZURE_API_VERSION`: If you are using Azure's OpenAI service to access DALL-E, these environment variables specify the API version for DALL-E 3 and DALL-E 2, respectively. Azure may have specific API version strings that need to be set to ensure compatibility with their services.
0 commit comments