Mailing-List: contact users-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@httpd.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=dk20050327; d=ix.netcom.com;
  b=CpXfwWV8FJfbDhOakoIl4ikvssrs7VlRiHY4+ER0DY0NjQ2yhY7JF6wXx04hu/Js;
  h=Received:Reply-To:From:To:Cc:Subject:Date:Organization:Message-ID:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Mailer:Thread-Index:X-MimeOLE:In-Reply-To:X-ELNK-Trace:X-Originating-IP;
Reply-To: <gregplatt@ix.netcom.com>
From: "Greg Platt - Platt Consultants" <GregPlatt@ix.netcom.com>
To: "'Joseph S D Yao'" <jsdy@tux.org>
Cc: <users@httpd.apache.org>
Date: Tue, 2 Sep 2008 15:27:54 -0600
Organization: Platt Consultants
Message-ID: <031301c90d42$c3585b00$0200a8c0@gregsrocket>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: AckNPv7BRhqcj5w9QL+Nfw4gLCLFFQAAYyHA
In-Reply-To: <20080902165927.B28867@gwyn.tux.org>
Subject: RE: [users@httpd] Why do I need /var/www as DocumentRoot & www-data
 as www owner?

I'm not arguing for or against what Debian did. One thing I can say is their
approach provides an individual VirtualHost file for each domain. It thus
tends to isolate any damage that might be done in editing httpd.conf to a
single domain. It also makes it easy to disable one domain using their
a2dissite utility without any risk of affecting other domains.

Other than that, I honestly don't care. I was actually quite comfortable
with the httpd.conf approach too. I wasted several hours when I first got
involved with Debian trying to figure out exactly how their setup differed. 

Indeed, it was just after I'd gone through the struggle of figuring all that
out and had gotten my 3 test sites working under the Debian paradigm that
another Debian user remarked about my "unusual" directory structure and
expressed the opinion that the entire web structure "should be" owned by
www-data and all sites should be under /var/www. It was at that point that I
began to worry I had somehow misinterpreted Apache and Debian's intent here.


That's what eventually lead to my first post here today.

-----Original Message-----
From: Joseph S D Yao [mailto:jsdy@tux.org] 
Sent: Tuesday, September 02, 2008 2:59 PM
To: Greg Platt - Platt Consultants
Cc: users@httpd.apache.org
Subject: Re: [users@httpd] Why do I need /var/www as DocumentRoot & www-data
as www owner?

I have no clue why the Debian Etch distribution is set up as you
describe.

I do remember discussion about the time /var/www was first used, long
ago, about /var always being a read-write file system even if the others
were mounted read-only from some other medium [CD-ROM, NFS, etc.].  This
seemed to be at least part of the motivation.  But I can't speak for
Apache at all.


-- 
/*********************************************************************\
**
** Joe Yao				jsdy@tux.org - Joseph S. D. Yao
**
\*********************************************************************/


---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> 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