From: Rich Bowen Date: Tue, 26 May 2026 10:11:24 +0000 (+0000) Subject: docs: Modernize install.xml X-Git-Tag: 2.4.68-rc1-candidate~71 X-Git-Url: http://git.ipfire.org/gitweb/index.cgi?a=commitdiff_plain;h=908564169337e1bd5179985eecd6581a12ae06fb;p=thirdparty%2Fapache%2Fhttpd.git docs: Modernize install.xml - Remove mirrors reference and binary releases (both retired) - Update all external links to https - Update version examples to current 2.4.66/2.4.67 - Replace two-step gzip/tar with single tar xzf - Reword download section for source builds - Consolidate verification link to verification.html - Remove minimizing language (easy, simple, simply) - Add language="sh" to all highlight blocks - Update disk space: 200 MB build (was 50), 50 MB installed (was 10) - Replace deprecated ntpdate/xntpd with systemd-timesyncd/chrony - Remove outdated Perl 5.003 version floor - Update release examples from dead 2.0/2.2 to 2.4/2.6 - Update 'Mac OS X, Solaris' to 'macOS' - Requirements intro: 'building' → 'building and running' git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/2.4.x@1934638 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/install.xml b/docs/manual/install.xml index dfd4c20920..7776443e65 100644 --- a/docs/manual/install.xml +++ b/docs/manual/install.xml @@ -40,7 +40,7 @@ projects.

If you are upgrading from one minor version to the next (for - example, 2.4.8 to 2.4.9), please skip down to the upgrading section.

@@ -55,7 +55,7 @@
Installing on Fedora/CentOS/Red Hat Enterprise Linux
- + sudo dnf install httpd # Start service @@ -75,7 +75,7 @@ sudo systemctl restart httpd
Installing on Ubuntu/Debian
- + sudo apt install apache2 # Start service @@ -99,16 +99,17 @@ sudo systemctl restart apache2 Download - Download the latest release from http://httpd.apache.org/download.cgi + Download the latest release from https://httpd.apache.org/download.cgi Extract - $ gzip -d httpd-NN.tar.gz
- $ tar xvf httpd-NN.tar
- $ cd httpd-NN + +$ tar xzf httpd-NN.tar.gz +$ cd httpd-NN + @@ -157,21 +158,21 @@ sudo systemctl restart apache2
Don't see your favorite platform mentioned - here? Come help us + here? Come help us improve this doc.
Requirements -

The following requirements exist for building Apache httpd:

+

The following requirements exist for building and running Apache httpd:

APR and APR-Util
Make sure you have APR and APR-Util already installed on your system. If you don't, or prefer to not use the system-provided versions, download the latest versions of both APR and APR-Util - from Apache APR, unpack + from Apache APR, unpack them into /httpd_source_tree_root/srclib/apr and /httpd_source_tree_root/srclib/apr-util (be sure the directory names do not have version numbers; for example, the APR distribution must be under /httpd_source_tree_root/srclib/apr/) and use @@ -182,7 +183,7 @@ sudo systemctl restart apache2
Perl-Compatible Regular Expressions Library (PCRE)
This library is required but no longer bundled with httpd. - Download the source code from http://www.pcre.org, + Download the source code from https://www.pcre.org, or install a Port or Package. If your build system can't find the pcre-config script installed by the PCRE build, point to it using the --with-pcre parameter. On some platforms, @@ -191,18 +192,18 @@ sudo systemctl restart apache2 of PCRE.
Disk Space
-
Make sure you have at least 50 MB of temporary free disk +
Make sure you have at least 200 MB of temporary free disk space available. After installation the server occupies - approximately 10 MB of disk space. The actual disk space + approximately 50 MB of disk space. The actual disk space requirements will vary considerably based on your chosen configuration options, any third-party modules, and, of course, the size of the web site or sites that you have on the server.
ANSI-C Compiler and Build System
Make sure you have an ANSI-C compiler installed. The GNU C + href="https://gcc.gnu.org/">GNU C compiler (GCC) from the Free Software Foundation (FSF) + href="https://www.gnu.org/">Free Software Foundation (FSF) is recommended. If you don't have GCC then at least make sure your vendor's compiler is ANSI compliant. In addition, your PATH must contain @@ -211,19 +212,18 @@ sudo systemctl restart apache2
Accurate time keeping
Elements of the HTTP protocol are expressed as the time of day. So, it's time to investigate setting some time - synchronization facility on your system. Usually the - ntpdate or xntpd programs are used for - this purpose which are based on the Network Time Protocol (NTP). - See the NTP + synchronization facility on your system. Most modern Linux + distributions provide systemd-timesyncd or + chrony for this purpose. See the NTP homepage for more details about NTP software and public time servers.
-
Perl 5 +
Perl 5 [OPTIONAL]
For some of the support scripts like apxs or dbmmanage (which are - written in Perl) the Perl 5 interpreter is required (versions - 5.003 or newer are sufficient). If no Perl 5 interpreter is found by the + written in Perl) the Perl 5 interpreter is required. + If no Perl 5 interpreter is found by the configure script, you will not be able to use the affected support scripts. Of course, you will still be able to build and use Apache httpd.
@@ -232,36 +232,29 @@ sudo systemctl restart apache2
Download -

The Apache HTTP Server can be downloaded from the Apache HTTP Server - download site, which lists several mirrors. Most users of - Apache on unix-like systems will be better off downloading and - compiling a source version. The build process (described below) is - easy, and it allows you to customize your server to suit your needs. - In addition, binary releases are often not up to date with the latest - source releases. If you do download a binary, follow the instructions - in the INSTALL.bindist file inside the distribution.

+

If you choose to build from source, start by downloading + the source tarball from the Apache HTTP Server + download site. The build process (described below) + allows you to customize your server to suit your + needs.

After downloading, it is important to verify that you have a complete and unmodified version of the Apache HTTP Server. This can be accomplished by testing the downloaded tarball against the - PGP signature. Details on how to do this are available on the download - page and an extended example is available describing the use of - PGP.

+ PGP signature. Details on how to do this are available on the + verification + page.

Extract -

Extracting the source from the Apache HTTP Server tarball is a - simple matter of uncompressing, and then untarring:

+

Extract the source from the Apache HTTP Server tarball:

-$ gzip -d httpd-NN.tar.gz -$ tar xvf httpd-NN.tar +$ tar xzf httpd-NN.tar.gz @@ -283,7 +276,7 @@ $ tar xvf httpd-NN.tar steps. This is not necessary for official releases.)

To configure the source tree using all the default options, - simply type ./configure. To change the default + type ./configure. To change the default options, configure accepts a variety of variables and command line options.

@@ -311,8 +304,7 @@ $ tar xvf httpd-NN.tar to a dash. Similarly, you can disable modules with the --disable-module option. Be careful when using these options, since configure cannot warn you - if the module you specify does not exist; it will simply ignore the - option.

+ if the module you specify does not exist; it will ignore the option.

In addition, it is sometimes necessary to provide the configure script with extra information about the @@ -348,7 +340,7 @@ $ CC="pgcc" CFLAGS="-O2" \

Build

Now you can build the various parts which form the Apache - package by simply running the command:

+ package by running:

$ make @@ -384,8 +376,8 @@ $ CC="pgcc" CFLAGS="-O2" \

Have a look at the Apache manual under PREFIX/docs/manual/ or consult http://httpd.apache.org/docs/&httpd.docs;/ for the most recent + href="https://httpd.apache.org/docs/&httpd.docs;/" + >https://httpd.apache.org/docs/&httpd.docs;/ for the most recent version of this manual and a complete reference of available configuration directives.

@@ -411,14 +403,14 @@ $ CC="pgcc" CFLAGS="-O2" \

The first step in upgrading is to read the release announcement and the file CHANGES in the source distribution to find any changes that may affect your site. When changing between - major releases (for example, from 2.0 to 2.2 or from 2.2 to 2.4), + major releases (for example, from 2.4 to 2.6), there will likely be major differences in the compile-time and run-time configuration that will require manual adjustments. All modules will also need to be upgraded to accommodate changes in the module API.

Upgrading from one minor version to the next (for example, from - 2.2.55 to 2.2.57) is easier. The make install + 2.4.66 to 2.4.67) is easier. The make install process will not overwrite any of your existing documents, log files, or configuration files. In addition, the developers make every effort to avoid incompatible changes in the @@ -469,8 +461,7 @@ $ PREFIX/bin/apachectl -k start

A large number of third parties provide their own packaged distributions of the Apache HTTP Server for installation on particular platforms. This includes the various Linux distributions, - various third-party Windows packages, Mac OS X, Solaris, and many - more.

+ various third-party Windows packages, macOS, and many more.

Our software license not only permits, but encourages, this kind of redistribution. However, it does result in a situation where the