You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/en/docs/deployment/general/subscription-management/licensing-apps.md
+9-7Lines changed: 9 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,7 +23,7 @@ Unlicensed apps, running outside Mendix Cloud, have some restrictions. These res
23
23
24
24
¹ More information on the capabilities of different license options is available on [Mendix Platform Pricing](https://www.mendix.com/pricing).
25
25
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 enduser 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.
27
27
28
28
³ Depending on the configuration of your chosen cloud, a container and runtime may be restarted if it appears unhealthy because the runtime has stopped.
29
29
@@ -169,17 +169,19 @@ For more instructions on how to do this, see [Linux Deployment](/developerportal
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:
173
173
174
174
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:
176
176
177
177
```bash
178
178
# License configuration
179
-
runtime.params {
180
-
License.LicenseID = <licenseId>
181
-
License.LicenseKey = <license_Key
179
+
runtime {
180
+
license {
181
+
id =
182
+
key =
183
+
}
182
184
}
183
185
```
184
186
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`forthe license related to your deployment target, or by creating a separate config file.
0 commit comments