Packages repository for Red Hat Enterprise Linux и CentOS

CodeIT is software development company (including web-based solutions). Therefore, we regularly need actual server software versions with support for advanced contemporary features. For example, NGINX and Apache httpd, built for industrial distributions with HTTP/2 and brotli compression support. But, we were not able to find ready-to-use packages. That’s why we built our own repository for RHEL/CentOS distributions and you are welcome to use it:

Version Supported architectures
6.x x86_64
7.x x86_64

To enable automatic packages update for Linux, please be sure to configure yum repository for RHEL/CentOS distributions.

Ready-to-use binary packages

To configure yum repository for RHEL/CentOS, please download repo file for EL6 or EL7 to /etc/yum.repos.d/ directory. Please consider the following shell command that will determine system version and download proper file:

cd /etc/yum.repos.d && wget https://repo.codeit.guru/codeit.el`rpm -q --qf "%{VERSION}" $(rpm -q --whatprovides redhat-release)`.repo

If you want to see the list of available packages, you can view the repository. Please also note that some packages in our repository rely on libraries can be found in EPEL repository (some of them are apr-util and libnghttp for Apache httpd). So, the easiest way to use our builds of  Apache HTTPd is to add EPEL repository, if you still do not have it:

yum install -y epel-release

Pre-Built Packages for Mainline version

To configure yum repository for RHEL/CentOS, please download repo file for EL6 or EL7 to /etc/yum.repos.d/ directory. Please consider the following shell command that will determine system version and download proper file:

cd /etc/yum.repos.d && wget https://repo.codeit.guru/codeit.mainline.el`rpm -q --qf "%{VERSION}" $(rpm -q --whatprovides redhat-release)`.repo

If you want to see the list of available packages, you can view the mainline-repository.

Why should I use this repository?

Here we will publish the latest version of nginx (from “mainline” and “stable” branches). Why these builds are better than official ones?

  • We built them statically against OpenSSL 1.0.2 that contains support for ALPN (features http2 negotiation at the stage of TLS connection establishment). It is important for us, since May 2016 Google Chrome cancels NPN support. Those who have not ALPN, remain with plain HTTP/1.1 over SSL without http2.
  • Content compression support using brotli built via plug ngx_brotli + libbrotli (built as a separate package).

We’re now watching the version openssl, nginx and we regularly update our buils on regular basis. In the future we plan to expand the list of software products, please check our blog regularly. Of course, SRPMs are available in the repository. Initial version is built against OpenSSL 1.0.2h. Packages in the repository are signed with our GPG-key, our public key is here.

Leave a Reply

Your email address will not be published. Required fields are marked *