You will likely find an answer to your question here.
It’s simple. The GetPageSpeed repository saves you both time and money.
Instead of having to compile software manually, doing it wrong, and spending much labor in the process – use our production-grade packages.
Our NGINX/Varnish packages are built with high performance and security in mind.
Ever heard of NGINX-Plus? We’re better.
The GetPageSpeed repository is your way to the enterprise NGINX build with 50+ modules so you can set up the top-notch high-performance web server in minutes.
If you are serious to run your websites in production, you will appreciate the nearly free subscription price (compared to $2.5k+ NGINX-Plus).
GetPageSpeed provides far more than NGINX module packages alone, for a funny subscription price.
With the GetPageSpeed repository you can literally extend your CentOS/RHEL system with pretty much everything that you need for a fast and secure server setup:
All of that is available once you subscribe. We don’t abandon a single package. Everything is consistent, up-to-date, stable, and production-ready.
NGINX-Plus is a feature-rich build of NGINX and its modules which come as a package repository.
The GetPageSpeed repository is a better NGINX-Plus alternative because it costs a lot less and provides more features.
Of course. Make sure you have the extra repo enabled before installing them:
sudo yum -y install yum-utils
sudo yum-config-manager --enable getpagespeed-extras-mainline
Then install modules as usual, e.g.:
sudo yum -y install nginx-module-security
The mainline branch of NGINX has far more frequent updates than the stable one.
For this or other reasons, you may want to downgrade to the stable branch.
sudo yum-config-manager --disable getpagespeed-extras-mainline
sudo yum -y downgrade "nginx*"
No. You do not need to have the RPM repository from nginx.org/packages.
The GetPageSpeed repository includes both NGINX and dynamic modules for it.
If you had nginx
from nginx.org, you don’t have to uninstall it or do anything special about it.
If you want to benefit from SELinux fixes (e.g. 1) available in the nginx
package by GetPageSpeed, simply reinstall it.
This would replace the package you had from nginx.org
with ours. No configuration will be lost:
yum reinstall nginx
There might be some “leftover” packages related to NGINX.
Be sure to clean up EPEL’s NGINX module packages:
yum remove $(yum list installed | grep 'nginx.*@epel' | awk '{ print $1 }')
If you’re not sure about it, don’t run it. Things will work either way (c).
Simply allocate an Elastic IP and specify it while signing up here.
You can submit NGINX modules for continuous build in our system here.
The modules are rebuilt with every module and NGINX release, within 24 hrs.
Our repository signs both RPM packages and repository metadata with our GPG signature. So you know you’re getting the genuine builds.
By default, yum
will only check signatures on packages themselves. You can also instruct it to check the signature of the repository’s metadata. To do this, run:
sed -i 's@repo_gpgcheck=.*@repo_gpgcheck=1@' /etc/yum.repos.d/getpagespeed-extras.repo
Worth noting that in RHEL 8+, dnf config-manager
grew smart enough to handle wildcards so it’s cleaner to use:
dnf config-manager --setopt repo_gpgcheck=1 "getpagespeed-*" --save
RHEL (unlike CentOS), does not have the required EPEL repository configuration in the base repositories. So it must be installed prior to installing the GetPageSpeed release package, as such:
RHEL=$(rpm -E %{rhel})
sudo yum install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-$RHEL.noarch.rpm
sudo yum-config-manager --enable epel
sudo yum -y install https://extras.getpagespeed.com/release-latest.rpm
It is a supported OS. Prior to installing the GetPageSpeed release package, run:
amazon-linux-extras install epel
In general, the GetPageSpeed repository has perfect compatibility with the base OS repositories, as well as the EPEL repository.
The GetPageSpeed repository is likewise perfect for building your own web stack without a control panel.
Beware of the following known compatibility issues with control panels:
clearmage2
due to not providing PHP capability in their PHP packages (ridiculous packaging from cPanel)If you have another question, we are happy to receive your email and assist.