Skip to main content

Package Repository Install

Repository installs are the standard production choice because they simplify upgrades and dependency management.

Why repository installation is preferred​

When you install from the vendor repository, your package manager can track versions, dependencies, and upgrades. That makes long-term maintenance much safer than copying binaries manually or compiling from source without a strong reason.

What the bootstrap step does​

The repository bootstrap command adds the LiteSpeed package source to your system so your package manager knows where to fetch OpenLiteSpeed and related packages.

wget -O - https://repo.litespeed.sh | sudo bash
sudo apt update
sudo apt install openlitespeed lsphp84 lsphp84-common lsphp84-mysql

Why lsphp packages matter​

Installing openlitespeed gives you the web server itself. Installing lsphp packages gives you the PHP runtime that many sites expect. If you skip lsphp, static sites can still work, but PHP applications will not.

RHEL-family note​

On AlmaLinux, Rocky Linux, and related distributions, the package names may be similar but installation uses dnf or yum rather than apt.

Suggested first-day package set​

  • openlitespeed
  • one lsphp version
  • the matching common package
  • database extension packages if your application needs them

Example thought process​

If you are preparing a simple WordPress server, you might want:

  • openlitespeed
  • one supported lsphp version
  • MySQL or MariaDB-related PHP extensions
  • additional PHP extensions required by your application

After installation​

  • Access WebAdmin on port 7080
  • Set the admin password with admpass.sh
  • Confirm the HTTP listener on port 80

You may also want to confirm the installed PHP binary path, because you will use it later when creating external app definitions or checking version alignment.

Validation checklist​

  • package installation finished cleanly
  • service starts without immediate errors
  • default page responds on port 80
  • WebAdmin responds on port 7080
  • the chosen lsphp binary exists where expected

Operational advice for production​

Keep a short installation record for each server:

  • install date
  • distro and version
  • installed OpenLiteSpeed package version
  • installed lsphp version
  • any non-default package additions

That tiny bit of documentation helps a lot during future upgrades.

Upgrade advantage​

This installation method pays off later. When security or bug-fix updates arrive, you can use standard package workflows instead of building a custom upgrade process from scratch.

Key risk to avoid​

Do not casually mix repository-managed packages with hand-built binaries unless you fully understand the consequences. Mixed installation methods often create confusing upgrade and path problems.

Key takeaway​

Use repository packages when you want a maintainable, predictable OpenLiteSpeed deployment.