DiegolAmaral

After setting up a password for Redis in the Docker container and adding it to the MISP Core configuration file, the following error occurred. #### Steps to Reproduce 1. Configure...

> @Diogo-Rego @yaleman new PR is ready (and should work correctly AFAIK). Please test: #107 ```cmd redis-1 | 1:C 12 Aug 2024 10:04:39.532 # WARNING Memory overcommit must be enabled!...

* docker compose file used ```yaml version: '3' services: # This is capable to relay via gmail, Amazon SES, or generic relays # See: https://hub.docker.com/r/ixdotai/smtp mail: image: ixdotai/smtp environment: -...

@ostefano even adding the redis password to the .env, it is not adding the redis password to the config.php as it continues to give the same problem * error.log ```logs...

@ostefano ok, I'll test the background more

@ostefano implement it in my code and when building my image in Gitlab the redis password worked https://gitlab.com/Diogo-Rego/misp-boilerplate/-/tree/diego-redispassword?ref_type=heads

Apparently my docker gave priority to the image and not the build image

@ostefano Was the redis password supposed to be shown? for safety it would be better not to show it in the logs ```cmd misp-core-1 | Enforcing initialisation setting 'Plugin.ZeroMQ_redis_password' to...

@ostefano I've already tested redis with and without a password and didn't find any problems. The problem I had was that Docker Compose gave priority to the image and not...

I understand your concern. The idea was to avoid constantly modifying the MISP codebase and to enable more flexibility by using environment variables, making it easier to handle deployments with...