Mailing-List: contact docs-dev-help@perl.apache.org; run by ezmlm
Precedence: bulk
Date: Tue, 2 Jul 2002 08:45:08 -0500 (CDT)
From: Randy Kobes <randy@theoryx5.uwinnipeg.ca>
To: Stas Bekman <stas@stason.org>
cc: Per Einar Ellefsen <per.einar@skynet.be>, Thomas Klausner <domm@zsi.at>,
        <docs-dev@perl.apache.org>
Subject: Re: Mirrors
In-Reply-To: <3D21A95C.6080709@stason.org>
Message-ID: <Pine.LNX.4.33.0207020832440.8127-100000@theoryx5.uwinnipeg.ca>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Tue, 2 Jul 2002, Stas Bekman wrote:

> Per Einar Ellefsen wrote:
> > At 13:42 02.07.2002, Randy Kobes wrote:
> >>
> >> Is there a reason each mirror has to build the site from
> >> cvs? Couldn't the master site be placed under rsync, for
> >> example, and the mirrors just mirror that?
> >
> > Because we're only updating the HTML so often, the CVS version is the
> > one that's up to date.
>
> well actually that's not the reason. we don't expect mirrors to be more
> up to date then the master site
>
> > Furthermore, if the search has to be set up
> > anyway, does it cost that much to use CVS too?
>
> the problem is in the index files which may not be cross-platform. If
> you ignore search then yes you could rsync.
>
> but if you ignore search it's going to broken.
>
> if we hardcode perl.apache.org/search then those who want local search
> need to mangle templates.

Having a local search seems worthwhile ... Since the index files
aren't guaranteed to be cross-platform, that would mean building
them on the mirrors, which looks like it can be done with an
rsynced html tree and swish.conf. Then if perl.apache.org/search
isn't hardcoded, the mirror could just install the search
templates ...

best regards,
randy


---------------------------------------------------------------------
To unsubscribe, e-mail: docs-dev-unsubscribe@perl.apache.org
For additional commands, e-mail: docs-dev-help@perl.apache.org