jim 00/10/04 08:39:24
Modified: htdocs/manual configuring.html
htdocs/manual/mod core.html
Log:
Add info about config files can actually point to config directories :)
Revision Changes Path
1.4 +10 -0 httpd-docs-1.3/htdocs/manual/configuring.html
Index: configuring.html
===================================================================
RCS file: /home/cvs/httpd-docs-1.3/htdocs/manual/configuring.html,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- configuring.html 2000/09/21 21:23:10 1.3
+++ configuring.html 2000/10/04 15:39:22 1.4
@@ -30,6 +30,16 @@
files. Changes to the main configuration files are only recognized by
Apache when it is started or restarted.
+<P>New with Apache 1.3.13 is a feature where if any configuration
+file is actually a directory, Apache will enter that directory
+and parse any files (and subdirectories) found there as configuration
+files. One possible use for this would be to add VirtualHosts
+by creating small configuration files for each host, and placing
+them in such a configuration directory. Thus, you can add or
+remove VirtualHosts without editing any files at all, simply
+adding or deleting them. This makes automating such processes
+much easier.
+
<P>
The server also reads a file containing mime document types; the
filename is set by the <A HREF="mod/mod_mime.html#typesconfig"
1.174 +14 -3 httpd-docs-1.3/htdocs/manual/mod/core.html
Index: core.html
===================================================================
RCS file: /home/cvs/httpd-docs-1.3/htdocs/manual/mod/core.html,v
retrieving revision 1.173
retrieving revision 1.174
diff -u -r1.173 -r1.174
--- core.html 2000/09/25 02:36:05 1.173
+++ core.html 2000/10/04 15:39:23 1.174
@@ -126,8 +126,14 @@
Historically, this file only contained
<A HREF="#directory"><Directory></A> sections; in fact it can now
contain any server directive allowed in the <EM>server config</EM> context.
-<P><HR>
+<P>New in Apache 1.3.13 is the feature that if <CODE>AccessConfig</CODE>
+points to a directory, rather than a file, Apache will read all
+files in that directory, and any subdirectory, and parse those
+as configuration files.
+
+<P>See also <A HREF="#resourceconfig">ResourceConfig</A>.<P><HR>
+
<H2><A NAME="accessfilename">AccessFileName directive</A></H2>
<!--%plaintext <?INDEX {\tt AccessFileName} directive> -->
<A
@@ -2472,9 +2478,14 @@
Historically, this file contained most directives except for server
configuration directives and <A HREF="#directory"><Directory></A>
sections; in fact it can now contain any server directive allowed in the
-<EM>server config</EM> context.<P>
+<EM>server config</EM> context.
+
+<P>New in Apache 1.3.13 is the feature that if <CODE>ResourceConfig</CODE>
+points to a directory, rather than a file, Apache will read all
+files in that directory, and any subdirectory, and parse those
+as configuration files.
-See also <A HREF="#accessconfig">AccessConfig</A>.<P><HR>
+<P>See also <A HREF="#accessconfig">AccessConfig</A>.<P><HR>
<H2><A NAME="rlimit">RLimitCPU</A> <A NAME="rlimitcpu">directive</A></H2>
<!--%plaintext <?INDEX {\tt RLimitCPU} directive> -->
