
* localization + api-endpoint * docs: added firebase documentation * chore: icons * chore: SettingsTabs * feat: account pannel; fix: gear icons * docs: position update * feat: firebase * feat: plugin support * route * fixed bugs with firebase and moved a lot of files * chore(DALLE3): using UUID v4 * feat: support for social strategies; moved '/images' path * fix: data ignored * gitignore update * docs: update firebase guide * refactor: Firebase - use singleton pattern for firebase initialization, initially on server start - reorganize imports, move firebase specific files to own service under Files - rename modules to remove 'avatar' redundancy - fix imports based on changes * ci(DALLE/DALLE3): fix tests to use logger and new expected outputs, add firebase tests * refactor(loadToolWithAuth): pass userId to tool as field * feat(images/parse): feat: Add URL Image Basename Extraction Implement a new module to extract the basename of an image from a given URL. This addition includes the function, which parses the URL and retrieves the basename using the Node.js 'url' and 'path' modules. The function is documented with JSDoc comments for better maintainability and understanding. This feature enhances the application's ability to handle and process image URLs efficiently. * refactor(addImages): function to use a more specific regular expression for observedImagePath based on the generated image markdown standard across the app * refactor(DALLE/DALLE3): utilize `getImageBasename` and `this.userId`; fix: pass correct image path to firebase url helper * fix(addImages): make more general to match any image markdown descriptor * fix(parse/getImageBasename): test result of this function for an actual image basename * ci(DALLE3): mock getImageBasename * refactor(AuthContext): use Recoil atom state for user * feat: useUploadAvatarMutation, react-query hook for avatar upload * fix(Toast): stack z-order of Toast over all components (1000) * refactor(showToast): add optional status field to avoid importing NotificationSeverity on each use of the function * refactor(routes/avatar): remove unnecessary get route, get userId from req.user.id, require auth on POST request * chore(uploadAvatar): TODO: remove direct use of Model, `User` * fix(client): fix Spinner imports * refactor(Avatar): use react-query hook, Toast, remove unnecessary states, add optimistic UI to upload * fix(avatar/localStrategy): correctly save local profile picture and cache bust for immediate rendering; fix: firebase init info message (only show once) * fix: use `includes` instead of `endsWith` for checking manual query of avatar image path in case more queries are appended (as is done in avatar/localStrategy) --------- Co-authored-by: Danny Avila <messagedaniel@protonmail.com>
3.3 KiB
title | description | weight |
---|---|---|
🍃 Manage Your Database | How to install and configure Mongo Express to securely access and manage your MongoDB database in Docker. | -5 |
Manage Your MongoDB Database with Mongo Express
To enhance the security of your data, external ports for MongoDB are not exposed outside of the docker environment. However, you can safely access and manage your MongoDB database using Mongo Express, a convenient web-based administrative interface. Follow this guide to set up Mongo Express in your Docker environment.
Mongo-Express Setup
Mongo Express allows you to interact with your MongoDB database through your browser. To set it up, perform the following steps:
-
Create a new file named
docker-compose.override.yml
in the same directory as your maindocker-compose.yml
file for LibreChat. -
Copy the following contents into the
docker-compose.override.yml
file:
version: '3.4'
services:
mongo-express:
image: mongo-express
container_name: mongo-express
environment:
ME_CONFIG_MONGODB_SERVER: mongodb
ME_CONFIG_BASICAUTH_USERNAME: admin
ME_CONFIG_BASICAUTH_PASSWORD: password
ports:
- '8081:8081'
depends_on:
- mongodb
restart: always
-
Security Notice: Before using this configuration, replace
admin
andpassword
with a unique username and password for accessing Mongo Express. These credentials should be strong and not easily guessable to prevent unauthorized access. -
Save the
docker-compose.override.yml
file and run the following command from the directory where yourdocker-compose.yml
file is located to start Mongo-Express along with your other Docker services:
docker-compose up -d
This command will merge the docker-compose.override.yml
with your docker-compose.yml
and apply the configuration.
- 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 forME_CONFIG_BASICAUTH_USERNAME
andME_CONFIG_BASICAUTH_PASSWORD
.
Removing Mongo Express
If you wish to remove Mongo-Express from your Docker environment, follow these straightforward steps:
-
Navigate to the directory containing your
docker-compose.yml
anddocker-compose.override.yml
files. -
Bring down the current Docker environment, which will stop and remove all running containers defined in the
docker-compose.yml
anddocker-compose.override.yml
files. Use the following command:
docker-compose down
-
Now you can either rename or delete the
docker-compose.override.yml
file, which contains the Mongo Express configuration. -
Finally, bring your Docker environment back up, which will now exclude Mongo Express:
docker-compose up -d
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.