Redmine

I was able to enter the information in the configuration.yaml file and the email notification configuration screen was enabled so I could configure it.
I can't say that this is what made it work, but I put the variables relating to the configuration of my SMTP server in the environment variables of my Deployment.
And I also changed the name of my Configmap that I had placed in configuration.yaml. I changed it to configuration-mail.yml.

Problem solved.

Régis Corrêa Silva wrote:

Hello everyone, I installed Redmine 5.05 on Rancher 2.6.6 and I am unable to change the information in the file: /config/configuration.yaml, to be able to configure the sending of email notifications.
As the file is inside a container, I created a configmap to make changes to the file. However, when trying to map the volume to the default address: /bitnami/redmine, the Rancher error gives an already mapped volume, as Redmine creates a volume to save the images in this volume. And if I change the address to: /bitnami/redmine/config, another error occurs saying that it cannot locate the database.yaml file at the address: /opt/bitnami/redmine/config/database.yaml.
The container is only created if I map the volume to another folder, like: /config. In this case, the configuration.yaml file is created, but has no effect on the system configuration. So I am unable to activate the email notification settings screen.
Which only shows the message: "Email sending is not configured, and notifications are inactive.
Configure your SMTP server in the config/configuration.yml file and restart the application to activate them."
I'm putting this configuration in configmap:
.
.
.

Has anyone had a similar problem or am I doing it wrong?

Thank you very much in advance.

Just to complete the previous answer, in addition to adding the environment variables to the deployment, I needed to delete the volume in the Persistent Volume Claim (PVC), so that the configuration.yaml file was updated with the settings I made in Configmap.
I don't think this is the correct way, having to delete the volume where all the images that were added to the tasks are saved, but it was the way it worked.