| docs

Appearance

Application Runtimes ​

Application Runtimes is where you install the Node.js, Python, and Ruby versions that customers can run applications on. An account can only pick a version this page has installed.

Overview ​

URL: /admin/settings/runtime-manager-versions

The page sits under Settings > CloudLinux as Application Runtimes.

The runtime manager listing available and installed versions per language

The header counts what the repositories offer against what this server has:

FigureMeaning
TotalEvery version the repositories offer.
InstalledVersions on this server.
AvailableVersions not installed yet.
RuntimesHow many languages are covered.

Check for new versions re-reads the repositories. Install all installs every offered version, and each language has its own Install all as well.

Installing a version ​

Each row names the version, whether it is installed, where it comes from, and the package behind it. Install adds it; Uninstall removes it.

Install what your customers actually ask for rather than everything. Each version is a package on the server, and a version nobody uses is still one more thing to keep updated.

The web server matters ​

Applications run on Apache, on OpenLiteSpeed, and, since panel 1.9.0, on LiteSpeed Enterprise in native mode. The panel decides by the web server it is set to, the one shown as Active engine on Web Server. Since panel 1.9.2 a server where no web server was ever chosen counts as Apache, also when OpenLiteSpeed is installed on it but does not serve. Updating to 1.9.2 records OpenLiteSpeed as the web server on a server where it already serves without ever having been chosen, so its applications keep being served.

Phusion Passenger on Apache ​

On Apache, applications are served by Phusion Passenger. While Apache is the web server and Passenger is missing, the page says so at the top:

  • Phusion Passenger is not installed - the runtimes below can be installed, but no application serves a request until Passenger is installed. Install Passenger installs it from this page: confirm with Install it, and the install log opens. Apache is restarted at the end of the install. It is the same install as the Phusion Passenger module in Modules.
  • Phusion Passenger is installed but not enabled in Apache - enable the Passenger module in MyApache, or applications are not served.

Since panel 1.9.2 the warning and Install Passenger also show on an Apache server where OpenLiteSpeed is installed but not serving; before, such a server was taken for an OpenLiteSpeed one.

While Passenger is missing, customers do not see Applications in their panel. Since panel 1.9.2 the client API also refuses to create an application then, with a message that says what is missing and where the administrator fixes it.

Under LiteSpeed Enterprise running as the Apache drop-in, the page says plainly that applications cannot be served: an application would answer with a directory listing instead of starting. Converting LiteSpeed to native mode, or switching the web server to Apache or OpenLiteSpeed, is what makes applications work.

Installing versions still works under LiteSpeed Enterprise. They are the interpreters the version selectors offer, and they will be there when the web server changes.

What the server reports ​

The page reports what is running, and says so when the application server is missing rather than implying everything is in place. On CloudLinux servers, the CloudLinux builds are preferred when no runtime version has been chosen. Since panel 1.9.0 the page also finds the CloudLinux alt-ruby versions installed on the server, so customers choose their Ruby version for Ruby applications on the Applications page.