Return-Path: X-Original-To: apmail-httpd-users-archive@www.apache.org Delivered-To: apmail-httpd-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 4E78B7DC7 for ; Tue, 6 Sep 2011 19:31:44 +0000 (UTC) Received: (qmail 29070 invoked by uid 500); 6 Sep 2011 19:31:41 -0000 Delivered-To: apmail-httpd-users-archive@httpd.apache.org Received: (qmail 29007 invoked by uid 500); 6 Sep 2011 19:31:40 -0000 Mailing-List: contact users-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: users@httpd.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list users@httpd.apache.org Received: (qmail 28999 invoked by uid 99); 6 Sep 2011 19:31:40 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Sep 2011 19:31:40 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of steve.j.swift@gmail.com designates 74.125.82.173 as permitted sender) Received: from [74.125.82.173] (HELO mail-wy0-f173.google.com) (74.125.82.173) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Sep 2011 19:31:34 +0000 Received: by wyf22 with SMTP id 22so6115206wyf.18 for ; Tue, 06 Sep 2011 12:31:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:content-type; bh=Um8NKbeof0/UUX84cMs8b9fM84vck7xmnRt9kyOnvEg=; b=RymiuGNDBoRru/owThujgIEeBYDctF1ZDotqRzOAOt0A+rvuCn3XbE7Isjr1ckod5x vWx7pXXl+FCnCVdn6Ls0Y2W/JLNp6dpTGNIY60Cu9lRs11+YYU/hw7WYUI/RiB1+uJ/w ciOsR4owhnFxrNSLJCjLESdtwlAaxeopKtA1o= Received: by 10.227.162.201 with SMTP id w9mr1282909wbx.28.1315337474105; Tue, 06 Sep 2011 12:31:14 -0700 (PDT) MIME-Version: 1.0 Sender: steve.j.swift@gmail.com Received: by 10.227.207.146 with HTTP; Tue, 6 Sep 2011 12:30:54 -0700 (PDT) In-Reply-To: References: From: Steve Swift Date: Tue, 6 Sep 2011 20:30:54 +0100 X-Google-Sender-Auth: WBtjzthkwKeFyH0OSv5H0PgWRKM Message-ID: To: users@httpd.apache.org Content-Type: multipart/alternative; boundary=20cf3002570ce763a804ac4ade21 X-Virus-Checked: Checked by ClamAV on apache.org Subject: Re: [users@httpd] httpd-vhosts.conf using include --20cf3002570ce763a804ac4ade21 Content-Type: text/plain; charset=ISO-8859-1 You can arrange them any way that you like. The include statement includes the referenced file(s) at the point where it is encountered. You could expand all of this out, and create a single httpd.conf file, and it would work exactly the same. Or you could have an include statement for every line in your config, with each included file containing just one line. The include mechanism makes it easier to manage, is all. Things I use "include" for: 1. You can remove "stuff" fron your config by commenting out the "include". So if you add a new Vhost, and define it in a new Include file, then you can remove it with a very simple comment character if it causes problems. 2. It allows you to replace identical sequences of statements in two or more places, for example, you might apply some common ScriptAlias statements across multiple Vhosts (for example, "Scriptalias /test /var/www/cgi-bin/text.cgi" might be useful in all of your Vhosts. If you add it using "Include", then a single change to the include file will update all of your virtualhosts. On 6 September 2011 19:55, Norman Fournier wrote: > Hello, > > I am working on rebuilding a web server after a crash. In my previous > httpd.conf file, include was used to point to virtual host .conf files. In > this httpd.conf file it points to httpd-vhosts.conf for virtual hosting. My > question is should I include my vitual hosts in the httpd-vhosts.conf or can > I use still include in the httpd-vhosts.conf file to point to individual > .conf files for my virtual hosts? > > I have googled for the answer but each examples includes the virtual host > in httpd-vhosts.conf. > > Thank you for your help. > > Norman > --- > www: http://www.normanfournier.com > facebook: http://www.facebook.com/normanfournierdotcom > linkedin: http://www.linkedin.com/profile/view?id=18127460 > youtube: http://www.youtube.com/user/normanfournier > > > > --------------------------------------------------------------------- > The official User-To-User support forum of the Apache HTTP Server Project. > See for more info. > To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org > " from the digest: users-digest-unsubscribe@httpd.apache.org > For additional commands, e-mail: users-help@httpd.apache.org > > -- Steve Swift http://www.swiftys.org.uk --20cf3002570ce763a804ac4ade21 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable You can arrange them any way that you lik= e. The include statement includes the referenced file(s) at the point where= it is encountered. You could expand all of this out, and create a single h= ttpd.conf file, and it would work exactly the same. Or you could have an in= clude statement for every line in your config, with each included file cont= aining just one line.

The include mechanism makes it easier to manage, is all. Thi= ngs I use "include" for:

1. You can remove "= ;stuff" fron your config by commenting out the "include". So= if you add a new Vhost, and define it in a new Include file, then you can = remove it with a very simple comment character if it causes problems.

2. It allows you to replace identical sequences of stat= ements in two or more places, for example, you might apply some common Scri= ptAlias statements across multiple Vhosts (for example, "Scriptalias /= test /var/www/cgi-bin/text.cgi" might be useful in all of your Vhosts.= If you add it using "Include", then a single change to the inclu= de file will update all of your virtualhosts.

On 6 September 2011 19:55, Norman Fourn= ier <norm= an@normanfournier.com> wrote:
Hello,

I am working on rebuilding a web server after a crash. In my previous httpd= .conf file, include was used to point to virtual host .conf files. In this = httpd.conf file it points to httpd-vhosts.conf for virtual hosting. My ques= tion is should I include my vitual hosts in the httpd-vhosts.conf or can I = use still include in the httpd-vhosts.conf file to point to individual .con= f files for my virtual hosts?

I have googled for the answer but each examples includes the virtual host i= n httpd-vhosts.conf.

Thank you for your help.

Norman
---
www: http://www= .normanfournier.com
facebook: http://www.facebook.com/normanfournierdotcom
linkedin: http://www.linkedin.com/profile/view?id=3D18127460
youtube: http://www.youtube.com/user/normanfournier



---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.<= br> See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
=A0 " =A0 from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org




--
Steve Swift<= br>http://www.swiftys.org.uk
--20cf3002570ce763a804ac4ade21--