From b3666891751e9bbf1eceb547f2e858347a7627ad Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?M=C3=A1rio=20Serrador?= <61971372+mruiserrmendix@users.noreply.github.com> Date: Tue, 16 Jun 2026 08:56:40 +0200 Subject: [PATCH 1/5] Revise license configuration in documentation Updated license configuration syntax and added environment variable references. --- .../general/subscription-management/licensing-apps.md | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/content/en/docs/deployment/general/subscription-management/licensing-apps.md b/content/en/docs/deployment/general/subscription-management/licensing-apps.md index 4ca4495f554..055fc0f643e 100644 --- a/content/en/docs/deployment/general/subscription-management/licensing-apps.md +++ b/content/en/docs/deployment/general/subscription-management/licensing-apps.md @@ -176,10 +176,12 @@ To activate the license on a Mendix app using Portable App Distribution on eithe ```bash # License configuration -runtime.params { - License.LicenseID = - License.LicenseKey = Date: Wed, 17 Jun 2026 16:29:23 +0200 Subject: [PATCH 2/5] Fix language for environment variable explanation --- .../general/subscription-management/licensing-apps.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/deployment/general/subscription-management/licensing-apps.md b/content/en/docs/deployment/general/subscription-management/licensing-apps.md index 055fc0f643e..38b4ed5831a 100644 --- a/content/en/docs/deployment/general/subscription-management/licensing-apps.md +++ b/content/en/docs/deployment/general/subscription-management/licensing-apps.md @@ -184,4 +184,4 @@ runtime { } ``` -The values for these properties can also be passed by using environment variables `RUNTIME_LICENSE_ID` and `RUNTIME_LICENSE_KEY` 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. From ab82c6acb55d01cc0f8a95e5f919bc58bc2169c6 Mon Sep 17 00:00:00 2001 From: Mark van Ments <35492184+MarkvanMents@users.noreply.github.com> Date: Wed, 17 Jun 2026 16:36:33 +0200 Subject: [PATCH 3/5] Improve grammar --- .../general/subscription-management/licensing-apps.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/deployment/general/subscription-management/licensing-apps.md b/content/en/docs/deployment/general/subscription-management/licensing-apps.md index 38b4ed5831a..15c4da80afc 100644 --- a/content/en/docs/deployment/general/subscription-management/licensing-apps.md +++ b/content/en/docs/deployment/general/subscription-management/licensing-apps.md @@ -169,7 +169,7 @@ 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: From 839f1faa36c7e955c5e695ae98b846183d92f597 Mon Sep 17 00:00:00 2001 From: MarkvanMents Date: Thu, 18 Jun 2026 15:46:55 +0200 Subject: [PATCH 4/5] Clarify what licenses are for. --- .../general/subscription-management/licensing-apps.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/en/docs/deployment/general/subscription-management/licensing-apps.md b/content/en/docs/deployment/general/subscription-management/licensing-apps.md index 15c4da80afc..4832b710b8f 100644 --- a/content/en/docs/deployment/general/subscription-management/licensing-apps.md +++ b/content/en/docs/deployment/general/subscription-management/licensing-apps.md @@ -169,10 +169,10 @@ 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 Docker, Cloud Foundry, or Unix-like servers, follow these steps: +To activate the license for 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: +2. Add the `LicenseID` and `LicenseKey` to your runtime configuration: ```bash # License configuration @@ -184,4 +184,4 @@ runtime { } ``` -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. +The values for these properties can also be passed by using the environment variables `RUNTIME_LICENSE_ID` and `RUNTIME_LICENSE_KEY` for the license related to your deployment target, or by creating a separate config file. From 2d7a3183429bb228665ec09934013ba1238923a2 Mon Sep 17 00:00:00 2001 From: MarkvanMents Date: Thu, 18 Jun 2026 15:48:43 +0200 Subject: [PATCH 5/5] Proofread --- .../general/subscription-management/licensing-apps.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/deployment/general/subscription-management/licensing-apps.md b/content/en/docs/deployment/general/subscription-management/licensing-apps.md index 4832b710b8f..c03975d42b2 100644 --- a/content/en/docs/deployment/general/subscription-management/licensing-apps.md +++ b/content/en/docs/deployment/general/subscription-management/licensing-apps.md @@ -23,7 +23,7 @@ Unlicensed apps, running outside Mendix Cloud, have some restrictions. These res ¹ More information on the capabilities of different license options is available on [Mendix Platform Pricing](https://www.mendix.com/pricing). -² End-users of your app are classified as either internal or external. You must report this classification for licensing purposes by [implementing User Metering](/developerportal/deploy/implementing-user-metering/) for each end user of your app. The [`USAGE_METRICS_EMAIL_FIELDS` custom variable](/developerportal/deploy/environments-details/#custom-environment-variables) is deprecated and should no longer be used for user classification. Use User Metering instead to ensure accurate and consistent user classification across your application portfolio. Only end users whose Mendix accounts are marked as **Active** are counted towards the number of end users of the app. +² End-users of your app are classified as either internal or external. You must report this classification for licensing purposes by [implementing User Metering](/developerportal/deploy/implementing-user-metering/) for each end-user of your app. The [`USAGE_METRICS_EMAIL_FIELDS` custom variable](/developerportal/deploy/environments-details/#custom-environment-variables) is deprecated and should no longer be used for user classification. Use User Metering instead to ensure accurate and consistent user classification across your application portfolio. Only end users whose Mendix accounts are marked as **Active** are counted toward the number of end users of the app. ³ Depending on the configuration of your chosen cloud, a container and runtime may be restarted if it appears unhealthy because the runtime has stopped.