X-Original-To: pgsql-advocacy-postgresql.org@localhost.postgresql.org Received: from localhost (neptune.hub.org [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 87D58D1B4A4; Wed, 14 Jan 2004 23:26:42 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 47880-07; Wed, 14 Jan 2004 19:26:13 -0400 (AST) Received: from hermes.indel.com.br (unknown [200.203.148.66]) by svr1.postgresql.org (Postfix) with ESMTP id 90E34D1B49B; Wed, 14 Jan 2004 19:26:09 -0400 (AST) Received: from localhost (localhost [127.0.0.1]) by hermes.indel.com.br (Postfix) with ESMTP id 48E00C4573; Wed, 14 Jan 2004 21:34:40 -0200 (BRST) Received: from qwerty (200-171-151-160.dsl.telesp.net.br [200.171.151.160]) by hermes.indel.com.br (Postfix) with ESMTP id 0BA2BC4572; Wed, 14 Jan 2004 21:34:22 -0200 (BRST) Date: Wed, 14 Jan 2004 21:25:45 -0200 (E. South America Daylight Time) From: "Ricardo Ryoiti S. Junior" To: Peter Eisentraut Cc: Robert Treat , Alvaro Herrera , "Marc G. Fournier" , pgsql-advocacy@postgresql.org Subject: Re: FTP Mirrors (was Re: Rewriting the website) In-Reply-To: <200401142358.06919.peter_e@gmx.net> Message-ID: References: <40014281.4060908@cs.msu.su> <200401142018.44331.peter_e@gmx.net> <1074115306.29165.373.camel@camel> <200401142358.06919.peter_e@gmx.net> X-X-Sender: suga@netbsd.com.br@mail.netbsd.com.br MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS 0.3.12 X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200401/251 X-Sequence-Number: 3433 Hi, On Wed, 14 Jan 2004, Peter Eisentraut wrote: > I think the directory structure should mirror exactly > ftp.postgresql.org, so I can go to ftp.xx.postgresql.org and find the > same things in the same places. If someone wants to mirror with > arbitrary directory structure, they can do that, but since you're going > to have to go through the web page anyway they don't have to carry the > postgresql.org domain at all. > Right now, virtually no mirrors follow that rule. Is it so hard to set > up virtual hosts on ftp servers? Regardless of virtualhosts, I think that ftp.postgresql.org's own FTP server should be structured like /pub/PostgreSQL/v7.4.1... That's how our mirror is setup and I believe that's the cleanest way to have more than one mirror in the same server. This is also a good practice, since not all (including ours) ftp daemons support virtual hosts. If we had all directories directly after /pub, there would be more than 30 subdirectories, all mixed up: NetBSD, PostgreSQL, etc. Thus, setting our mirror just like PostgreSQL's, without virtualhost, would be very confusing for our clients. I agree that every mirror should use the same directory structure, but asking everyone to place everything directly after /pub or setting up virtualhosts doesn't seem to be plausible, mainly because there're a lot of mirrors out there. So I think that the easiest (and cleanest) way is to change postgresql's ftp to /pub/postgresql, asking new and current mirrors to adopt that approach. It's much easier than asking for virtualhosts. Not just because I wouldn't have to change my setup :) but also because many projects with mirrors do that successfully. Or, at least a /pub/postgresql link to the actual mirror directory could be used... []s Ricardo.