Skip to content

Revise license configuration in documentation #11359

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

Open
mruiserrmendix wants to merge 3 commits into
base: development
Choose a base branch
from
+7 −5
Open

Revise license configuration in documentation #11359

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
b366689
Revise license configuration in documentation
mruiserrmendix Jun 16, 2026
1c0fcd1
Fix language for environment variable explanation
MarkvanMents Jun 17, 2026
ab82c6a
Improve grammar
MarkvanMents Jun 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
12 changes: 7 additions & 5 deletions content/en/docs/deployment/general/subscription-management/licensing-apps.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -169,17 +169,19 @@ For more instructions on how to do this, see [Linux Deployment](/developerportal

### Portable App Distribution{#portableappdistribution}

To activate the license on a Mendix app using Portable App Distribution on either Docker, Cloud Foundry, or Unix-like servers, follow these steps:
To activate the license on a Mendix app using Portable App Distribution on Docker, Cloud Foundry, or Unix-like servers, follow these steps:

1. Open the `$ConfigName.conf` in `etc/configurations`.
2.  Add the `LicenseID` and `LicenseKey` to your runtime configuration:

```bash
# License configuration
runtime.params {
License.LicenseID = <licenseId>
License.LicenseKey = <license_Key
runtime {
license {
   id =
    key =
  }
}
```

The values for these properties can also be passed by using environment variables for your deployment type, or by creating a separate config file.
The values for these properties can also be passed by using the environment variables `RUNTIME_LICENSE_ID` and `RUNTIME_LICENSE_KEY` for your deployment type, or by creating a separate config file.

@MarkvanMents MarkvanMents Jun 17, 2026

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What do you mean by environment variables for your deployment type?
We are just talking about PAD deployment here, so surely the customer just has one license ID and license key for PAD, which is what they should be putting here?

@mruiserrmendix mruiserrmendix Jun 17, 2026

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, we are just talking about PAD deployment.
My meaning of deployment type is Linux, Docker, K8S, CF

Loading