Information on the latest version of Apache can be found on the Apache web server at http://www.apache.org/. This will list the current release, any more recent beta-test release, together with details of mirror web and anonymous ftp sites.UnixWare users will want to consult build notes for various UnixWare versions before compiling.
modules.c') which simply has a list of them.
If you are satisfied with our standard module set, and expect to
continue to be satisfied with it, then you can just edit the stock
Makefile and compile as you have been doing previously. If you
like to select optional modules, however, you need to run the
To do this:
Configuration'. This contains the per-machine config settings of the Makefile, and also an additional section at the bottom which lists the modules which have been compiled in, and also names the files containing them. You will need to:
Note that DBM auth has to be explicitly configured in, if you want it; just uncomment the corresponding line.
This generates new versions of the Makefile and of modules.c. If you want to maintain multiple configurations, you can say, e.g.,
Using 'Configuration' as config file
% Configure -file Configuration.ai
Using alternate config file Configuration.ai
The modules we place in the Apache distribution are the ones we have tested and are used regularly by various members of the Apache development group. Additional modules contributed by members or third parties with specific needs or functions are available at <URL:http://www.apache.org/dist/contrib/modules/>. There are instructions on that page for linking these modules into the core Apache code.
src/directory. A binary distribution of Apache will supply this file.
The next step is to edit the configuration files for the server. In
the subdirectory called `conf' you should find distribution versions
of the three configuration files:
httpd.conf-dist. Copy them to
httpd.conf. This sets up general attributes about the
server; the port number, the user it runs as, etc. Next edit the
srm.conf file; this sets up the root of the document tree,
special functions like server-parsed HTML or internal imagemap parsing, etc.
Finally, edit the
access.conf file to at least set the base cases
Finally, make a call to httpd, with a -f to the full path to the httpd.conf file. I.e., the common case:
The server should be now running.
/usr/local/etc/apache/src/httpd -f /usr/local/etc/apache/conf/httpd.conf
By default the
access.conf files are
located by name; to specifically call them by other names, use the
ResourceConfig directives in