httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From di...@apache.org
Subject cvs commit: httpd-docs-1.3/htdocs/manual/mod core.html.en
Date Wed, 25 Sep 2002 23:05:37 GMT
dirkx       2002/09/25 16:05:37

  Modified:    htdocs/manual/mod core.html.en
  Log:
  Added *.conf wildcard based reading of config files.
  
  We propably at some point want to have a generic section
  on fnmatch wildcarding and point all those sections to that
  place.
  
  Revision  Changes    Path
  1.231     +29 -13    httpd-docs-1.3/htdocs/manual/mod/core.html.en
  
  Index: core.html.en
  ===================================================================
  RCS file: /home/cvs/httpd-docs-1.3/htdocs/manual/mod/core.html.en,v
  retrieving revision 1.230
  retrieving revision 1.231
  diff -u -r1.230 -r1.231
  --- core.html.en	27 Aug 2002 11:01:02 -0000	1.230
  +++ core.html.en	25 Sep 2002 23:05:37 -0000	1.231
  @@ -264,7 +264,7 @@
   
       <a href="directive-dict.html#Syntax"
       rel="Help"><strong>Syntax:</strong></a> AccessConfig
  -    <em>file-path</em>|<em>directory-path</em><br />
  +    <em>file-path</em>|<em>directory-path</em>|<em>wildcard-path</em><br
/>
        <a href="directive-dict.html#Default"
       rel="Help"><strong>Default:</strong></a> <code>AccessConfig
       conf/access.conf</code><br />
  @@ -303,9 +303,16 @@
   
       <p>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. Note that
  -    <emph>any</emph> file in the specified directory will be loaded as a
  -    configuration file, so make sure that you don't have stray files in
  +    subdirectory, and parse those as configuration files. 
  +    </p>
  +    <p>Alternatively you can use a wildcard to limit the scope; i.e
  +    to only *.conf files.
  +    </p>
  +    <p>Note that by default <emph>any</emph> file in the specified 
  +    directory will be loaded as a configuration file.
  +    <p>
  +    </p>
  +    So make sure that you don't have stray files in
       this directory by mistake, such as temporary files created by your
       editor, for example.</p>
   
  @@ -1713,7 +1720,7 @@
   
       <h2><a id="include" name="include">Include directive</a></h2>
       <strong>Syntax:</strong> Include
  -    <em>file-path</em>|<em>directory-path</em><br />
  +    <em>file-path</em>|<em>directory-path</em>|<em>wildcard-path</em><br
/>
        <a href="directive-dict.html#Context"
       rel="Help"><strong>Context:</strong></a> server config<br />
        <a href="directive-dict.html#Status"
  @@ -1733,9 +1740,10 @@
       <code>Include</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>
  -
  +    <p>By using a wildcard this can be further limited to, say,
  +    just the '*.conf' files.
  +    </p>
       <p>Examples:</p>
  -
       <blockquote>
       <code>Include /usr/local/apache/conf/ssl.conf<br />
       Include /usr/local/apache/conf/vhosts/
  @@ -3005,7 +3013,7 @@
   
       <a href="directive-dict.html#Syntax"
       rel="Help"><strong>Syntax:</strong></a> ResourceConfig
  -    <em>file-path</em>|<em>directory-path</em><br />
  +    <em>file-path</em>|<em>directory-path</em>|<em>wildcard-path</em><br
/>
        <a href="directive-dict.html#Default"
       rel="Help"><strong>Default:</strong></a> <code>ResourceConfig
       conf/srm.conf</code><br />
  @@ -3043,11 +3051,19 @@
   
       <p>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. Note that
  -    <emph>any</emph> file in the specified directory will be loaded as a
  -    configuration file, so make sure that you don't have any stray files
  -    in this directory by mistake, such as temporary files created by
  -    your editor, for example.</p>
  +    subdirectory, and parse those as configuration files. 
  +    </p>
  +    <p>Alternatively you can use a wildcard to limit the scope; i.e
  +    to only *.conf files.
  +    </p>
  +    <p>Note that by default <emph>any</emph> file in the specified 
  +    directory will be loaded as a configuration file.
  +    <p>
  +    </p>
  +    So make sure that you don't have stray files in
  +    this directory by mistake, such as temporary files created by your
  +    editor, for example.</p>
  +
   
       <p>See also <a href="#accessconfig">AccessConfig</a>.</p>
       <hr />
  
  
  

Mime
View raw message