Strong Passwords for Database

caution

💡 In standalone mode in a private deployment, by default, the database components are built into the mirror and start with the microservice, and the database in the container is not accessible externally.

💥 If there is a need to map the database port from the container to the host for access, it is highly recommended to do so when the following three conditions are met, otherwise it is extremely risky for the database port to be exposed to the Internet!!!

1. Back up data regularly (to prevent unrecoverable data loss due to database hacking).

2. Set up access whitelist for database ports ( to restrict source addresses from accessing database ports).

3. Change the password to a strong one (Avoid special characters with regular meanings, such as "$", "&", "@", etc., otherwise they cannot be passed into the container; you can choose - or _).

📄️Change Default Password for MySQL

- The following steps take the root password as tC9S86SFWxga as an example. The root password must be modified in the actual configuration

📄️Change Default Password for Redis

- The following steps use the new password of Redis as f8K5ZT3aQXTb as an example. The Redis password must be modified in the actual configuration

📄️MongoDB Add Authentication

- Adding authentication will create two users, namely the root user of the admin library and the NAMEBRANDEN user of all business libraries.