Skip to content

Add security recommendation for secrets management #11929

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
katarzyna-koltun-mx merged 3 commits into from
Sep 17, 2026
Merged

Add security recommendation for secrets management #11929

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
fc52df1
Add security recommendation for secrets management
mruiserrmendix Sep 17, 2026
bef49ea
Update docker-pad.md
katarzyna-koltun-mx Sep 17, 2026
972ee79
Refactor security recommendation section
katarzyna-koltun-mx Sep 17, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 9 additions & 1 deletion content/en/docs/deployment/pad/docker-pad.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -163,11 +163,15 @@ services:
command: ["./bin/start", "etc/Default"]
```

### 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

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`

Expand Down Expand Up @@ -204,6 +208,10 @@ Alternatively, you can configure the Mendix Runtime by using a configuration fil
}
```

### 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

To use the configuration file, you can upload the configuration file to the configuration path:
Expand Down