From d9a2c3aade20226d7680692f5872bbe24edde65f Mon Sep 17 00:00:00 2001 From: Joshua Slive Date: Mon, 21 May 2001 20:31:37 +0000 Subject: [PATCH] Add a little more info on ways to enable modules, add an index, and clean up a few things. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@89189 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/install.html | 101 ++++++++++++++++++++++++++---------- docs/manual/install.html.en | 101 ++++++++++++++++++++++++++---------- 2 files changed, 148 insertions(+), 54 deletions(-) diff --git a/docs/manual/install.html b/docs/manual/install.html index a03eb3f836..c6933140bb 100644 --- a/docs/manual/install.html +++ b/docs/manual/install.html @@ -29,7 +29,28 @@ to achieve easy installation. Apache 2.0 now uses libtool and autoconf to create an environment that looks like many other Open Source projects.

-

Overview for the impatient

+ + +
+ +

Overview for the impatient

@@ -72,7 +93,7 @@ specified, it defaults to /usr/local/apache2.

described in more detail below, beginning with the requirements for compiling and installing Apache HTTPD.

-

Requirements

+

Requirements

The following requirements exist for building Apache:

@@ -89,7 +110,7 @@ ANSI-C compiler installed. The GNU C compiler (GCC) from the Free Software Foundation (FSF) is recommended (version 2.7.2 is fine). If you -don't have GCC then at least make sure your vendors compiler is ANSI +don't have GCC then at least make sure your vendor's compiler is ANSI compliant. In addition, your PATH must contain basic build tools such as make.

@@ -196,7 +217,7 @@ which will later be used to compile the server.

is to run ./configure --help. What follows is a brief description of most of the arguments and environment variables.

-

Environment Variables

+

Environment Variables

The autoconf build process uses several environment variables to configure the build environment. In general, these variables change @@ -246,7 +267,7 @@ linker. -

autoconf Output Options

+

autoconf Output Options

@@ -263,7 +284,7 @@ including the names of all the files examined.
-

Pathnames

+

Pathnames

There are currently two ways to configure the pathnames under which Apache will install its files. First, you can specify @@ -314,7 +335,7 @@ own. If you want to customize your install, you should edit the config.layout file and use the --enable-layout option.

-

Modules

+

Modules

Apache is a modular server. Only the most basic functionality is included in the core server. Extended features are available in @@ -348,15 +369,43 @@ and include the module MODULE. The identifier MODULE is the Module Identifier from the module documentation without the -"_module" string. To compile the module dynamically as a DSO, add the +"_module" string. To compile the module as a DSO, add the option =shared.

--disable-MODULE
Remove the module MODULE which would otherwise be compiled and included.
+
--enable-modules=MODULE-LIST
Compile and +include the modules listed in the space-separated +MODULE-LIST.
+ +
--enable-mods-shared=MODULE-LIST
Compile +and include the modules in the space-separated MODULE-LIST as +dynamically loadable (DSO) modules.
+ +

The MODULE-LIST in the --enable-modules and +--enable-mods-shared options is usually a space-separated list +of module identifiers. For example, to enable mod_dav and mod_info, you +can either use

+
+./configure --enable-dav --enable-info +
+

or, equivalently,

+
+./configure --enable-modules="dav info" +
+

In addition, the special keywords all +or most can be used to add all or most of the modules +in one step. You can then remove any modules that you do not want +with the --disable-MODULE option. For example, +to include all modules as DSOs with the exception of mod_info, you can use

+
+./configure --enable-mods-shared=all --disable-info +
+

In addition to the standard set of modules, Apache 2.0 also includes a choice of Multi-Processing Modules (MPMs). One, and only one MPM must be included in the compilation @@ -371,7 +420,7 @@ on the configure command line. -

Suexec

+

Suexec

Apache includes a support program called suexec which can be used to isolate user CGI @@ -379,9 +428,9 @@ programs. However, if suexec is improperly configured, it can cause serious security problems. Therefore, you should carefully read and consider the suexec documentation before implementing this feature.

- -

Building the package

+ +

Build

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

@@ -396,26 +445,25 @@ system, but this will vary widely depending on your hardware and the number of modules which you have enabled.

-

Installing the package

+

Install

Now its time to install the package under the configured -installation PREFIX (see --prefix option above) by running: -

- $ make install -
+installation PREFIX (see --prefix option above) +by running:
$ make install +

If you are upgrading, the installation will not overwrite your configuration files or documents.

-

Customizing the package

+

Customize

Next, you can customize your Apache HTTP server by editing the configuration files under -PREFIX/conf/.

+PREFIX/conf/.

-$ vi PREFIX/conf/httpd.conf +$ vi PREFIX/conf/httpd.conf

Have a look at the Apache manual under http://httpd.apache.org/docs/ for a complete reference of available configuration directives.

-

Testing the package

+

Test

Now you can start your Apache HTTP server by immediately running:

- $ PREFIX/bin/apachectl start + $ PREFIX/bin/apachectl start

and then you should be able to request your first document via URL -http://localhost/ (when you built and installed Apache as root) or -http://localhost:8080/ (when you built and installed Apache as a -regular user). The web page you see is located under the DocumentRoot which will usually -be PREFIX/htdocs/. Then stop -the server again by running:

+be PREFIX/htdocs/. Then stop the server again by running:

-
$ PREFIX/bin/apachectl stop
+
$ PREFIX/bin/apachectl stop +
diff --git a/docs/manual/install.html.en b/docs/manual/install.html.en index a03eb3f836..c6933140bb 100644 --- a/docs/manual/install.html.en +++ b/docs/manual/install.html.en @@ -29,7 +29,28 @@ to achieve easy installation. Apache 2.0 now uses libtool and autoconf to create an environment that looks like many other Open Source projects.

-

Overview for the impatient

+ + +
+ +

Overview for the impatient

Download
@@ -72,7 +93,7 @@ specified, it defaults to /usr/local/apache2.

described in more detail below, beginning with the requirements for compiling and installing Apache HTTPD.

-

Requirements

+

Requirements

The following requirements exist for building Apache:

@@ -89,7 +110,7 @@ ANSI-C compiler installed. The GNU C compiler (GCC) from the Free Software Foundation (FSF) is recommended (version 2.7.2 is fine). If you -don't have GCC then at least make sure your vendors compiler is ANSI +don't have GCC then at least make sure your vendor's compiler is ANSI compliant. In addition, your PATH must contain basic build tools such as make.

@@ -196,7 +217,7 @@ which will later be used to compile the server.

is to run ./configure --help. What follows is a brief description of most of the arguments and environment variables.

-

Environment Variables

+

Environment Variables

The autoconf build process uses several environment variables to configure the build environment. In general, these variables change @@ -246,7 +267,7 @@ linker. -

autoconf Output Options

+

autoconf Output Options

@@ -263,7 +284,7 @@ including the names of all the files examined.
-

Pathnames

+

Pathnames

There are currently two ways to configure the pathnames under which Apache will install its files. First, you can specify @@ -314,7 +335,7 @@ own. If you want to customize your install, you should edit the config.layout file and use the --enable-layout option.

-

Modules

+

Modules

Apache is a modular server. Only the most basic functionality is included in the core server. Extended features are available in @@ -348,15 +369,43 @@ and include the module MODULE. The identifier MODULE is the Module Identifier from the module documentation without the -"_module" string. To compile the module dynamically as a DSO, add the +"_module" string. To compile the module as a DSO, add the option =shared.

--disable-MODULE
Remove the module MODULE which would otherwise be compiled and included.
+
--enable-modules=MODULE-LIST
Compile and +include the modules listed in the space-separated +MODULE-LIST.
+ +
--enable-mods-shared=MODULE-LIST
Compile +and include the modules in the space-separated MODULE-LIST as +dynamically loadable (DSO) modules.
+ +

The MODULE-LIST in the --enable-modules and +--enable-mods-shared options is usually a space-separated list +of module identifiers. For example, to enable mod_dav and mod_info, you +can either use

+
+./configure --enable-dav --enable-info +
+

or, equivalently,

+
+./configure --enable-modules="dav info" +
+

In addition, the special keywords all +or most can be used to add all or most of the modules +in one step. You can then remove any modules that you do not want +with the --disable-MODULE option. For example, +to include all modules as DSOs with the exception of mod_info, you can use

+
+./configure --enable-mods-shared=all --disable-info +
+

In addition to the standard set of modules, Apache 2.0 also includes a choice of Multi-Processing Modules (MPMs). One, and only one MPM must be included in the compilation @@ -371,7 +420,7 @@ on the configure command line. -

Suexec

+

Suexec

Apache includes a support program called suexec which can be used to isolate user CGI @@ -379,9 +428,9 @@ programs. However, if suexec is improperly configured, it can cause serious security problems. Therefore, you should carefully read and consider the suexec documentation before implementing this feature.

- -

Building the package

+ +

Build

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

@@ -396,26 +445,25 @@ system, but this will vary widely depending on your hardware and the number of modules which you have enabled.

-

Installing the package

+

Install

Now its time to install the package under the configured -installation PREFIX (see --prefix option above) by running: -

- $ make install -
+installation PREFIX (see --prefix option above) +by running:
$ make install +

If you are upgrading, the installation will not overwrite your configuration files or documents.

-

Customizing the package

+

Customize

Next, you can customize your Apache HTTP server by editing the configuration files under -PREFIX/conf/.

+PREFIX/conf/.

-$ vi PREFIX/conf/httpd.conf +$ vi PREFIX/conf/httpd.conf

Have a look at the Apache manual under http://httpd.apache.org/docs/ for a complete reference of available configuration directives.

-

Testing the package

+

Test

Now you can start your Apache HTTP server by immediately running:

- $ PREFIX/bin/apachectl start + $ PREFIX/bin/apachectl start

and then you should be able to request your first document via URL -http://localhost/ (when you built and installed Apache as root) or -http://localhost:8080/ (when you built and installed Apache as a -regular user). The web page you see is located under the DocumentRoot which will usually -be PREFIX/htdocs/. Then stop -the server again by running:

+be PREFIX/htdocs/. Then stop the server again by running:

-
$ PREFIX/bin/apachectl stop
+
$ PREFIX/bin/apachectl stop +
-- 2.50.1
Download