public inbox for [email protected]
help / color / mirror / Atom feedFrom: Marc G. Fournier <[email protected]>
To: Ricardo Ryoiti S. Junior <[email protected]>
Cc: Peter Eisentraut <[email protected]>
Cc: Robert Treat <[email protected]>
Cc: Alvaro Herrera <[email protected]>
Cc: Marc G. Fournier <[email protected]>
Cc: [email protected]
Subject: Re: FTP Mirrors (was Re: Rewriting the website)
Date: Wed, 14 Jan 2004 20:07:54 -0400 (AST)
Message-ID: <[email protected]> (raw)
In-Reply-To: <Pine.WNT.4.58.0401142109040.896@qwerty>
References: <[email protected]>
<[email protected]>
<1074115306.29165.373.camel@camel>
<[email protected]>
<Pine.WNT.4.58.0401142109040.896@qwerty>
I have nothing against making that change on the mail server, should have
thought of that long ago, but, then again, nobody else has either ...
This is going to involve a massive update on all the mirrors, since
effectively everything will be moving at once ... is this something
everyone agrees should happen, before I do it?
On Wed, 14 Jan 2004, Ricardo Ryoiti S. Junior wrote:
> 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.
>
----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email: [email protected] Yahoo!: yscrappy ICQ: 7615664
view thread (28+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
Subject: Re: FTP Mirrors (was Re: Rewriting the website)
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox