Skip to content

Revise license configuration in documentation#11359

Open
mruiserrmendix wants to merge 3 commits into
mendix:developmentfrom
mruiserrmendix:patch-26
Open

Revise license configuration in documentation#11359
mruiserrmendix wants to merge 3 commits into
mendix:developmentfrom
mruiserrmendix:patch-26

Conversation

@mruiserrmendix

Copy link
Copy Markdown
Collaborator

Updated license configuration syntax and added environment variable references.

Updated license configuration syntax and added environment variable references.

@MarkvanMents MarkvanMents left a comment

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.

@mruiserrmendix
Hi Mario,
One quick question below which wasn't clear to me.

```
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.

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?

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants