Skip to content

Commit 2c1d567

Browse files
authored
Merge pull request #11359 from mruiserrmendix/patch-26
Revise license configuration in documentation
2 parents 1ce9433 + 2d7a318 commit 2c1d567

1 file changed

Lines changed: 9 additions & 7 deletions

File tree

content/en/docs/deployment/general/subscription-management/licensing-apps.md

Lines changed: 9 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ Unlicensed apps, running outside Mendix Cloud, have some restrictions. These res
2323

2424
¹ More information on the capabilities of different license options is available on [Mendix Platform Pricing](https://www.mendix.com/pricing).
2525

26-
² 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.
26+
² 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.
2727

2828
³ Depending on the configuration of your chosen cloud, a container and runtime may be restarted if it appears unhealthy because the runtime has stopped.
2929

@@ -169,17 +169,19 @@ For more instructions on how to do this, see [Linux Deployment](/developerportal
169169

170170
### Portable App Distribution{#portableappdistribution}
171171

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

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

177177
```bash
178178
# License configuration
179-
runtime.params {
180-
License.LicenseID = <licenseId>
181-
License.LicenseKey = <license_Key
179+
runtime {
180+
license {
181+
   id =
182+
    key =
183+
  }
182184
}
183185
```
184186
185-
The values for these properties can also be passed by using environment variables for your deployment type, or by creating a separate config file.
187+
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.

0 commit comments

Comments
 (0)