Skip to main content
Sign in

CloudLinux Knowledge Base

  1. CloudLinux
  2. CloudLinux OS
  3. PHP Selector

alt-PHP, Python,NodeJS, Ruby repositories changes in CloudLinux 10

Robert Asilbekov
  • Updated

With the release of CloudLinux 10 (CL10), you may notice new repositories on your system with names like alt-*-release. These are part of the new ALT-ELS delivery scheme.

This article explains what these repositories are, why they were introduced, and how they function on your server.

What are ALT-ELS Repositories?

ALT-ELS is the new unified method used by the CloudLinux team to distribute "ALT" packages.

  • Purpose: In the context of CloudLinux OS, these repositories provide the various versions of software used by our Selectors (PHP, Python, NodeJS, and Ruby).

  • Why the change? Previously, ALT packages were mirrored across multiple locations for different products (CLOS, ELS, etc.). To simplify updates and ensure consistency, we have created a single, unified location for all new package releases.

How are they Deployed?

The deployment is handled automatically by the cldeploy script during the system conversion process.

  1. Initial Setup: The alt-common-release package is installed along with the standard cloudlinux-release.

  2. Module Installation: The script then installs the specific release packages for each language:

    • els-php-release

    • els-python-release

    • els-nodejs-release

    • els-ruby-release

Note: If you see a log message stating: "Unable to set up PHP/NodeJS/Python/Ruby auxiliary repositories", the installation failed. In this case, please contact CloudLinux Support.

Authentication and Access

Unlike standard CloudLinux repositories, ALT-ELS repositories require separate authentication. This is because these packages are shared across different products (CloudLinux OS, Imunify360, and standalone ELS) under different licensing schemes.

How it works for you:

If your machine is registered with a valid license, access is handled automatically.

  1. JWT Token: Upon successful registration, a primary CloudLinux JWT (JSON Web Token) is generated on your machine.

  2. DNF Integration: The rhn-client-tools package (version 3.0.2-1 or higher) automatically links this token to your package manager's variables:

    • /etc/dnf/vars/phpelstoken

    • /etc/dnf/vars/altpythonelstoken

    • /etc/dnf/vars/altrubyelstoken

    • /etc/dnf/vars/altnodejselstoken

  3. Server-Side Logic: When you run an update, DNF uses these tokens within the repository URLs to verify your access.

Frequently Asked Questions (FAQ)

Do I need to configure these tokens manually? No. As long as you have a valid license and your machine is registered, the system creates the necessary symlinks automatically.

Will this be applied to older CloudLinux versions? Yes. While CloudLinux 10 is the first to use this scheme, older systems (like CL7 or CL8) will follow this model in the future.

What happens if my license expires? Since access depends on a valid JWT token, you will lose access to the ALT-ELS repositories (and thus updates for PHP/Python/NodeJS Selectors) if the license is no longer active.

Comments

0 comments

Please sign in to leave a comment.

Related articles