Skip to content

Commit 5b3c133

Browse files
committed
ELS for Languages: general updates/fixes
1 parent 346b432 commit 5b3c133

File tree

1 file changed

+43
-43
lines changed

1 file changed

+43
-43
lines changed

docs/els-for-languages/README.md

Lines changed: 43 additions & 43 deletions
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ TuxCare provides Endless Lifecycle Support through four years after the EOL date
2222
| AlmaLinux | 8.x 64-bit, 9.x 64-bit |
2323
| Ubuntu | 16.04 64-bit, 18.04 64-bit, 20.04 64-bit, 22.04 64-bit|
2424
| Debian | 10, 11, 12 |
25-
| Windows | Windows Server 2019, 2025 |
25+
| Windows | Windows Server 2019, 2022, 2025 |
2626
Other distros upon request.
2727

2828

@@ -32,7 +32,7 @@ Other distros upon request.
3232

3333
**Ubuntu:** 5.6.40, 7.0.33, 7.1.33, 7.2.34, 7.3.33, 7.4.33, 8.0.30, 8.1.27, 8.2, 8.3
3434

35-
**Debian:** 10, 11, 12
35+
**Debian:** 5.6, 7.0, 7.1, 7.2, 7.3, 7.4, 8.0, 8.1, 8.2
3636

3737
**Windows:** 5.6, 7.4
3838

@@ -95,27 +95,27 @@ Description : PHP is an HTML-embedded scripting language.
9595
yum install alt-php73*
9696
```
9797

98-
To install all versions at the same time, use group:
98+
- To install all versions at the same time, use group:
9999

100100
```
101101
yum groupinstall alt-php
102102
```
103103

104104
#### Ubuntu
105105

106-
Download an installer script:
106+
1. Download an installer script:
107107

108108
```
109109
wget https://repo.cloudlinux.com/php-els/install-php-els-ubuntu-repo.sh
110110
```
111111

112-
Run the installer script with keys:
112+
2. Run the installer script with keys:
113113

114114
```
115115
bash install-php-els-ubuntu-repo.sh --license-key XXX-XXXXXXXXXXXX
116116
```
117117

118-
To ensure the installation has been completed successfully, run the following command. It should return the info about an available package. If information about the package will be available, it would mean that installation was successful. After that, updates will be available for installation from the repository using the usual apt upgrade command.
118+
3. To ensure the installation has been completed successfully, run the following command. It should return the info about an available package. If information about the package will be available, it would mean that installation was successful. After that, updates will be available for installation from the repository using the usual apt upgrade command.
119119

120120
```
121121
apt-cache show alt-php73-cli
@@ -146,7 +146,7 @@ Description-md5: 0d83f7bf7177d3376a59b73890c8494d
146146
```
147147
apt-get install alt-php73*
148148
```
149-
To install all versions at the same time, it is necessary to use the alt-php meta-package:
149+
- To install all versions at the same time, it is necessary to use the alt-php meta-package:
150150
```
151151
apt-get install alt-php
152152
```
@@ -201,7 +201,7 @@ oscap oval eval --results result.xml --report report.xml centos6-els-php-oval.xm
201201
202202
### PHP extensions list
203203
204-
You can find the list of the supported add-ons [here](https://docs.cloudlinux.com/shared/alt-ea_packages/#bundled-php-extensions).
204+
You can find the list of the supported add-ons [here](https://docs.cloudlinux.com/cloudlinuxos/alt-ea_packages/#bundled-php-extensions).
205205
206206
### How to use PHP-ELS
207207
@@ -393,13 +393,13 @@ TuxCare provides Endless Lifecycle Support through four years after the EOL date
393393
Other distros upon request.
394394
395395
### Supported versions
396-
**EL6, 7, 8, 9**: alt-python 2.7, 3.3, 3.4, 3.5, 3.6, 3.7, 3.8, 3.9, 3.10, 3.11, 3.12, 3.13
397-
**debian 9 and 10**: 3.5, 3.8, 3.11
398-
**debian 11 and 12**: 3.8, 3.11
399-
**Ubuntu 16 and 18**: 3.5, 3.8, 3.11
400-
**Ubuntu 20**: 3.7, 3.8, 3.10, 3.11, 3.12
401-
**Ubuntu 22**: 3.8, 3.11, 3.13
402-
**Ubuntu 24**: 3.8, 3.11
396+
* **EL6, 7, 8, 9**: alt-python 2.7, 3.3, 3.4, 3.5, 3.6, 3.7, 3.8, 3.9, 3.10, 3.11, 3.12, 3.13
397+
* **Debian 9 and 10**: 3.5, 3.8, 3.11
398+
* **Debian 11 and 12**: 3.8, 3.11
399+
* **Ubuntu 16 and 18**: 3.5, 3.8, 3.11
400+
* **Ubuntu 20**: 3.7, 3.8, 3.10, 3.11, 3.12
401+
* **Ubuntu 22**: 3.8, 3.11, 3.13
402+
* **Ubuntu 24**: 3.8, 3.11
403403
404404
### Installation instructions of yum repositories
405405
@@ -414,7 +414,7 @@ sh install-python-els-repo.sh --license-key XXX-XXXXXXXXXXXX
414414
```
415415
3. Verify that the installation was successful.
416416
417-
To ensure the installation has been completed successfully, run the following command. It should return the info about an available package. If information about the package will be available, it would mean that installation was successful. After that, updates will be available for installation from the repository using the usual yum upgrade command.
417+
To ensure the installation has been completed successfully, run the following command. It should return the info about an available package. If information about the package will be available, it would mean that installation was successful. After that, updates will be available for installation from the repository using the usual yum upgrade command.
418418
```
419419
yum info python2
420420

@@ -436,7 +436,7 @@ Description  : Python 2 is an old version of the language that is incompatible
436436
```
437437
yum install python2 --enablerepo crb
438438
```
439-
Once installed, you can use python2 in the usual way.
439+
5. Once installed, you can use python2 in the usual way.
440440
```python
441441
$ python2
442442
Python 2.7.18 (default, Jun 30 2022, 00:00:00)
@@ -449,15 +449,15 @@ Hello, World!
449449
### Installation instructions of a local mirror
450450

451451
We provide the ability to create local mirrors of Python for ELS updates.
452-
To obtain the access to the local mirroring, provide your External IP address to your Account Manager or send it to [[email protected]](mailto:[email protected]).
452+
* To obtain the access to the local mirroring, provide your External IP address to your Account Manager or send it to [[email protected]](mailto:[email protected]).
453453

454-
To create a local mirror of the repository with security updates via `rsync`, use the following:
454+
* To create a local mirror of the repository with security updates via `rsync`, use the following:
455455

456456
```
457457
rsync://repo.cloudlinux.com/PYTHON_ELS/
458458
```
459459

460-
Example of creating a local mirror for all supported OS versions:
460+
* Example of creating a local mirror for all supported OS versions:
461461

462462
```
463463
rsync -avSHP --delete rsync://repo.cloudlinux.com/PYTHON_ELS/ .
@@ -508,7 +508,7 @@ TuxCare will make commercially reasonable efforts to adhere to the following gui
508508
- **Low-severity CVEs:** Patches provided within 90 days
509509
- TuxCare may offer a mitigation strategy as an alternative to a direct code fix.
510510

511-
### **Incident Reporting and Response Timeframe**
511+
### Incident Reporting and Response Timeframe
512512

513513
Customers can report vulnerabilities by submitting a ticket through the TuxCare Support Portal <https://tuxcare.com/support-portal/>. TuxCare commits to providing an initial response to any reported issue within 3 days.
514514

@@ -548,7 +548,7 @@ You need username and password in order to use TuxCare ELS Spring repository. An
548548

549549
**Maven**
550550

551-
If you are using Maven as your build automation tool, you will need to make changes in your `${MAVEN_HOME}/settings.xml` file. If the file does not already exist in your Maven home directory (`${MAVEN_HOME}`), you should create one. Open the `settings.xml` file with a text editor and include the following configuration:
551+
* If you are using Maven as your build automation tool, you will need to make changes in your `${MAVEN_HOME}/settings.xml` file. If the file does not already exist in your Maven home directory (`${MAVEN_HOME}`), you should create one. Open the `settings.xml` file with a text editor and include the following configuration:
552552

553553
```
554554
<?xml version="1.0" encoding="UTF-8"?>
@@ -563,16 +563,16 @@ If you are using Maven as your build automation tool, you will need to make chan
563563
</settings>
564564
```
565565

566-
Set your credentials via the following enviromnent variables:
566+
* Set your credentials via the following environment variables:
567567

568568
```
569569
export USERNAME=your-username
570570
export PASSWORD=your-password
571571
```
572572

573-
Here `your-username` and `your-password` are your credentials mentioned in the [Step 1](https://github.com/cloudlinux/securechain-java/blob/main/details/integration_guide.md#step-1-get-user-credntials) .
573+
Here `your-username` and `your-password` are your credentials mentioned in the [Step 1](#step-1-get-user-credentials).
574574

575-
You may choose an arbitrary allowed value instead of `repository-id` and use the same value in the following snippet from your `pom.xml` file:
575+
* You may choose an arbitrary allowed value instead of `repository-id` and use the same value in the following snippet from your `pom.xml` file:
576576

577577
```
578578
<repositories>
@@ -583,11 +583,11 @@ You may choose an arbitrary allowed value instead of `repository-id` and use the
583583
</repositories>
584584
```
585585

586-
An example of maven project you can find [here](https://github.com/cloudlinux/securechain-java/blob/main/examples/maven) . Do not forget to set the enviromnet variables.
586+
* An example of maven project you can find [here](https://github.com/cloudlinux/securechain-java/blob/main/examples/maven). Do not forget to set the environment variables.
587587

588588
**Gradle**
589589

590-
If you are using Gradle as your build automation tool, make sure to include the following configuration in your project setup:
590+
* If you are using Gradle as your build automation tool, make sure to include the following configuration in your project setup:
591591

592592
```
593593
repositories {
@@ -601,16 +601,16 @@ If you are using Gradle as your build automation tool, make sure to include the
601601
}
602602
```
603603

604-
Set your credentials via the following enviromnent variables:
604+
* Set your credentials via the following environment variables:
605605

606606
```
607607
export ORG_GRADLE_PROJECT_USERNAME=your-username
608608
export ORG_GRADLE_PROJECT_PASSWORD=your-password
609609
```
610610

611-
Here `your-username` and `your-password` are your credentials mentioned in the [Step 1](https://github.com/cloudlinux/securechain-java/blob/main/details/integration_guide.md#step-1-get-user-credntials) .
611+
Here `your-username` and `your-password` are your credentials mentioned in the [Step 1](#step-1-get-user-credentials).
612612

613-
An example of gradle project you can find [here](https://github.com/cloudlinux/securechain-java/blob/main/examples/gradle) . Do not forget to set the enviromnet variables.
613+
* An example of gradle project you can find [here](https://github.com/cloudlinux/securechain-java/blob/main/examples/gradle). Do not forget to set the environment variables.
614614

615615
### Verification
616616

@@ -1589,7 +1589,7 @@ TuxCare will make commercially reasonable efforts to adhere to the following gui
15891589
- **Low-severity CVEs:** Patches provided within 90 days
15901590
- TuxCare may offer a mitigation strategy as an alternative to a direct code fix.
15911591

1592-
### **Incident Reporting and Response Timeframe**
1592+
### Incident Reporting and Response Timeframe
15931593

15941594
Customers can report vulnerabilities by submitting a ticket through the TuxCare Support Portal <https://tuxcare.com/support-portal/>. TuxCare commits to providing an initial response to any reported issue within 3 days.
15951595

@@ -1621,13 +1621,13 @@ This guide outlines the steps needed to integrate the TuxCare ELS for Apache Tom
16211621
### Steps
16221622

16231623
### Step 1: Get user credentials
1624-
You need username and password in order to use TuxCare ELS Apache Tomcat repository. Anonymous access is disabled. To receive username and password please contact [email protected]
1624+
You need username and password in order to use TuxCare ELS Apache Tomcat repository. Anonymous access is disabled. To receive username and password please contact [[email protected]](mailto:[email protected]).
16251625

16261626
### Step 2: Create or Modify Your Build Tool Settings
16271627

16281628
**Maven**
16291629

1630-
If you are using Maven as your build automation tool, you will need to make changes in your `${MAVEN_HOME}/settings.xml` file. If the file does not already exist in your Maven home directory (`${MAVEN_HOME}`), you should create one. Open the `settings.xml` file with a text editor and include the following configuration:
1630+
* If you are using Maven as your build automation tool, you will need to make changes in your `${MAVEN_HOME}/settings.xml` file. If the file does not already exist in your Maven home directory (`${MAVEN_HOME}`), you should create one. Open the `settings.xml` file with a text editor and include the following configuration:
16311631

16321632
```
16331633
<?xml version="1.0" encoding="UTF-8"?>
@@ -1642,16 +1642,16 @@ If you are using Maven as your build automation tool, you will need to make chan
16421642
</settings>
16431643
```
16441644

1645-
Set your credentials via the following enviromnent variables:
1645+
* Set your credentials via the following environment variables:
16461646

16471647
```
16481648
export USERNAME=your-username
16491649
export PASSWORD=your-password
16501650
```
16511651

1652-
Here `your-username` and `your-password` are your credentials mentioned in the [Step 1](https://github.com/cloudlinux/securechain-java/blob/main/details/integration_guide.md#step-1-get-user-credntials) .
1652+
Here `your-username` and `your-password` are your credentials mentioned in the [Step 1](#step-1-get-user-credentials-1).
16531653

1654-
You may choose an arbitrary allowed value instead of `repository-id` and use the same value in the following snippet from your `pom.xml` file:
1654+
* You may choose an arbitrary allowed value instead of `repository-id` and use the same value in the following snippet from your `pom.xml` file:
16551655

16561656
```
16571657
<repositories>
@@ -1662,11 +1662,11 @@ You may choose an arbitrary allowed value instead of `repository-id` and use the
16621662
</repositories>
16631663
```
16641664

1665-
An example of maven project you can find [here](https://github.com/cloudlinux/securechain-java/blob/main/examples/maven) . Do not forget to set the enviromnet variables.
1665+
* An example of maven project you can find [here](https://github.com/cloudlinux/securechain-java/blob/main/examples/maven). Do not forget to set the environment variables.
16661666

16671667
**Gradle**
16681668

1669-
If you are using Gradle as your build automation tool, make sure to include the following configuration in your project setup:
1669+
* If you are using Gradle as your build automation tool, make sure to include the following configuration in your project setup:
16701670

16711671
```
16721672
repositories {
@@ -1680,16 +1680,16 @@ If you are using Gradle as your build automation tool, make sure to include the
16801680
}
16811681
```
16821682

1683-
Set your credentials via the following enviromnent variables:
1683+
* Set your credentials via the following environment variables:
16841684

16851685
```
16861686
export ORG_GRADLE_PROJECT_USERNAME=your-username
16871687
export ORG_GRADLE_PROJECT_PASSWORD=your-password
16881688
```
16891689

1690-
Here `your-username` and `your-password` are your credentials mentioned in the [Step 1](https://github.com/cloudlinux/securechain-java/blob/main/details/integration_guide.md#step-1-get-user-credntials) .
1690+
Here `your-username` and `your-password` are your credentials mentioned in the [Step 1](#step-1-get-user-credentials-1).
16911691

1692-
An example of gradle project you can find [here](https://github.com/cloudlinux/securechain-java/blob/main/examples/gradle) . Do not forget to set the enviromnet variables.
1692+
* An example of gradle project you can find [here](https://github.com/cloudlinux/securechain-java/blob/main/examples/gradle). Do not forget to set the environment variables.
16931693

16941694
### Verification
16951695

@@ -1934,7 +1934,7 @@ The following commands are useful for managing and troubleshooting .NET installa
19341934
* Search for *.NET SDK* or *.NET Runtime* depending on what you’ve installed.
19351935
* Click on each entry and select **Uninstall**.
19361936
:::tip
1937-
During the uninstall, a **"Files in use"** window can appear. Select **"Do not close applications. A reboot will be required option"** and click **OK** to proceed.
1937+
During the uninstall, a **"Files in use"** window can appear. Select **"Do not close applications. A reboot will be required"** option and click **OK** to proceed.
19381938
:::
19391939
* A dialog window will appear. Click **Uninstall**. It should take a few minutes. When the process is finished, close the window.
19401940
@@ -1945,7 +1945,7 @@ The following commands are useful for managing and troubleshooting .NET installa
19451945
* Search for *.NET SDK* or *.NET Runtime* depending on what you’ve installed.
19461946
* Right-click on each entry and select **Uninstall**.
19471947
:::tip
1948-
During the uninstall, a **"Files in use"** window can appear. Select **"Do not close applications. A reboot will be required option"** and click **OK** to proceed.
1948+
During the uninstall, a **"Files in use"** window can appear. Select **"Do not close applications. A reboot will be required"** option and click **OK** to proceed.
19491949
:::
19501950
* A dialog window will appear. Click **Uninstall**. It should take a few minutes. When the process is finished, close the window.
19511951

0 commit comments

Comments
 (0)