From fc52df1735bab30145510aa2c1da88c7a8238c2c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?M=C3=A1rio=20Serrador?=
 <61971372+mruiserrmendix@users.noreply.github.com>
Date: Thu, 17 Sep 2026 09:13:26 +0200
Subject: [PATCH 1/3] Add security recommendation for secrets management

Added security recommendation regarding secret management in Docker Compose and configuration files.
---
 content/en/docs/deployment/pad/docker-pad.md | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/content/en/docs/deployment/pad/docker-pad.md b/content/en/docs/deployment/pad/docker-pad.md
index 0c4c6f07b3d..433a308f86b 100644
--- a/content/en/docs/deployment/pad/docker-pad.md
+++ b/content/en/docs/deployment/pad/docker-pad.md
@@ -163,11 +163,13 @@ services:
     command: ["./bin/start", "etc/Default"]
 ```
 
+**Security Recommendation:** Do not store secrets in plaintext within Docker Compose YAML files, Kubernetes Secret manifests, application configuration files, or source code repositories. If these files are accidentally committed to a repository, shared externally, or uploaded to another platform, credentials may be exposed. Use a dedicated secret management mechanism and inject secrets during deployment whenever possible.
+
 ### Running with Docker Compose
 
 To use this Docker Compose configuration, perform the following steps:
 
-1. Set your admin port password in the **M2EE_ADMIN_PASS** variable within your environment, or directly in the *docker-compose.yaml* file.
+1. Set your admin port password in the **M2EE_ADMIN_PASS** variable within your environment.
 2. Navigate to the directory containing your *docker-compose.yaml* file
 3. Run a command like the following: `docker compose -f docker_compose/Default.yaml up`
 
@@ -204,6 +206,8 @@ Alternatively, you can configure the Mendix Runtime by using a configuration fil
 }
 ```
 
+**Security Recommendation:** Do not store secrets in plaintext within Docker Compose YAML files, Kubernetes Secret manifests, application configuration files, or source code repositories. If these files are accidentally committed to a repository, shared externally, or uploaded to another platform, credentials may be exposed. Use a dedicated secret management mechanism and inject secrets during deployment whenever possible.
+
 ### Using the Configuration File
 
 To use the configuration file, you can upload the configuration file to the configuration path:

From bef49ea8aba6375d5e656f43c7ebda5d525c14e2 Mon Sep 17 00:00:00 2001
From: katarzyna-koltun-mx
 <108737161+katarzyna-koltun-mx@users.noreply.github.com>
Date: Thu, 17 Sep 2026 09:54:55 +0200
Subject: [PATCH 2/3] Update docker-pad.md

---
 content/en/docs/deployment/pad/docker-pad.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/content/en/docs/deployment/pad/docker-pad.md b/content/en/docs/deployment/pad/docker-pad.md
index 433a308f86b..b9d9d464ca6 100644
--- a/content/en/docs/deployment/pad/docker-pad.md
+++ b/content/en/docs/deployment/pad/docker-pad.md
@@ -163,7 +163,9 @@ services:
     command: ["./bin/start", "etc/Default"]
 ```
 
-**Security Recommendation:** Do not store secrets in plaintext within Docker Compose YAML files, Kubernetes Secret manifests, application configuration files, or source code repositories. If these files are accidentally committed to a repository, shared externally, or uploaded to another platform, credentials may be exposed. Use a dedicated secret management mechanism and inject secrets during deployment whenever possible.
+### Security Recommendations
+
+Do not store secrets in plain text within Docker Compose YAML files, Kubernetes Secret manifests, application configuration files, or source code repositories. If these files are accidentally committed to a repository, shared externally, or uploaded to another platform, credentials may be exposed. Use a dedicated secret management mechanism and inject secrets during deployment whenever possible.
 
 ### Running with Docker Compose
 

From 972ee799e822fb7a0bc0c060258730c850c9fd57 Mon Sep 17 00:00:00 2001
From: katarzyna-koltun-mx
 <108737161+katarzyna-koltun-mx@users.noreply.github.com>
Date: Thu, 17 Sep 2026 09:55:39 +0200
Subject: [PATCH 3/3] Refactor security recommendation section

Updated security recommendation formatting for clarity.
---
 content/en/docs/deployment/pad/docker-pad.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/content/en/docs/deployment/pad/docker-pad.md b/content/en/docs/deployment/pad/docker-pad.md
index b9d9d464ca6..90a422750a7 100644
--- a/content/en/docs/deployment/pad/docker-pad.md
+++ b/content/en/docs/deployment/pad/docker-pad.md
@@ -208,7 +208,9 @@ Alternatively, you can configure the Mendix Runtime by using a configuration fil
 }
 ```
 
-**Security Recommendation:** Do not store secrets in plaintext within Docker Compose YAML files, Kubernetes Secret manifests, application configuration files, or source code repositories. If these files are accidentally committed to a repository, shared externally, or uploaded to another platform, credentials may be exposed. Use a dedicated secret management mechanism and inject secrets during deployment whenever possible.
+### Security Recommendations 
+
+Do not store secrets in plain text within Docker Compose YAML files, Kubernetes Secret manifests, application configuration files, or source code repositories. If these files are accidentally committed to a repository, shared externally, or uploaded to another platform, credentials may be exposed. Use a dedicated secret management mechanism and inject secrets during deployment whenever possible.
 
 ### Using the Configuration File