From owner-freebsd-isp Tue Oct 27 05:50:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA19185 for freebsd-isp-outgoing; Tue, 27 Oct 1998 05:50:36 -0800 (PST) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from dfw-ix1.ix.netcom.com (dfw-ix1.ix.netcom.com [206.214.98.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA19179 for ; Tue, 27 Oct 1998 05:50:34 -0800 (PST) (envelope-from graeme@echidna.com) Received: (from smap@localhost) by dfw-ix1.ix.netcom.com (8.8.4/8.8.4) id HAA20178; Tue, 27 Oct 1998 07:49:53 -0600 (CST) Received: from prn-nj2-15.ix.netcom.com(199.183.207.79) by dfw-ix1.ix.netcom.com via smap (V1.3) id rma020143; Tue Oct 27 07:49:36 1998 Message-ID: <3635F8E4.2FF8@echidna.com> Date: Tue, 27 Oct 1998 08:46:28 -0800 From: Graeme Tait Organization: Echidna X-Mailer: Mozilla 2.02 (Win16; I) MIME-Version: 1.0 To: freebsd-isp@FreeBSD.ORG CC: info@boatbooks.com Subject: Directory arrangement (etc.) for multi-user web server Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm setting up a FreeBSD/Apache (or Stronghold-Apache for SSL) system to be a web/ftp/mail server. The system will eventually support a fair number of domains, some with their own IP addresses, some hosted under a single IP. As this is my first time at this, I'm wondering if there are any conventional ways of organizing things, for convenience, security (esp. with use of SSL), ease of backup, and so on. As far as WWW access is concerned, Apache itself seems quite flexible in this regard. For example, one host I use running FreeBSD has a symlink under each user account, like usr/home/user1/public_html --> usr/www/users/user1 usr/home/user2/public_html --> usr/www/users/user2 etc. and all the www accessible information is thus stored under usr/www . Daily gzipped user clog files are placed in a directory under usr/home/userx (presumably by a cron job). I have lots of other questions (e.g, regarding logs, user cgi access, ftp, email forwarding and POP), but perhaps there is some place this sort of thing is addressed without my having to reinvent the wheel? -- Graeme Tait - Echidna To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message