Skip to content

Commit 1013fa2

Browse files
dimodidimodi
authored andcommitted
fixes
1 parent e765eb7 commit 1013fa2

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

deployment/ci-cd-license-key.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -19,13 +19,13 @@ This article describes how to set up and activate your [Telerik UI for Blazor li
1919
The Telerik license activation process in CI/CD environments involves the following steps:
2020

2121
1. Go to the [License Keys page](https://www.telerik.com/account/your-licenses/license-keys) in your Telerik account and download your license key.
22-
1. Set an [environment variable](#creating-environment-variables) with one of the following names:
22+
1. Set an environment variable with either of the following names:
2323
* `TELERIK_LICENSE`—the value must be the Telerik license key string.
2424
* `TELERIK_LICENSE_PATH`—the value must be the full path to the license key file, including the license file name itself. `TELERIK_LICENSE_PATH` requires `Telerik.Licensing` version `1.4.9` and above. You can use it with Telerik UI for Blazor `8.1.0` and above.
2525

2626
In most cases, the recommended way to provide your license key to the `Telerik.Licensing` NuGet package in CI/CD environments is to use the `TELERIK_LICENSE` environment variable.
2727

28-
Use `TELERIK_LICENSE_PATH` or only a license file on Windows and Windows Server machines, which are managed directly through the operating system's user interface. Do not use the `TELERIK_LICENSE` environment variable in this case, due to the large variable value length.
28+
Use `TELERIK_LICENSE_PATH` or [only a license file](slug:installation-license-key#manual-installation) on Windows and Windows Server machines, which are managed directly through the operating system's user interface. Do not use the `TELERIK_LICENSE` environment variable in this case, due to the large variable value length.
2929

3030
> Treat the license key and the license file as secrets. Always store and retrieve them in a secure manner, according to the build platform's best practices.
3131

0 commit comments

Comments
 (0)