public inbox for [email protected]  
help / color / mirror / Atom feed
From: Dave Page <[email protected]>
To: Tom Lane <[email protected]>
Cc: Joshua D. Drake <[email protected]>
Cc: Greg Smith <[email protected]>
Cc: PostgreSQL-development <[email protected]>
Cc: PostgreSQL www <[email protected]>
Subject: Re: [HACKERS] Move the developers wiki?
Date: Wed, 12 Mar 2008 19:20:01 +0000
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>

On Wed, Mar 12, 2008 at 7:09 PM, Tom Lane <[email protected]> wrote:
> "Joshua D. Drake" <[email protected]> writes:
> > Tom Lane <[email protected]> wrote:
> >> That's not exactly what I'd call "keeping existing links working".
>
> > It is if we point developer. to wiki.
>
> Will that break anything else (ie, is that webserver serving anything
> but the wiki)?

No, thats one of the reasons why I'd like to move developer - this one
is not just on a dedicated apache instance, but a dedicated VM.

I don't see any reason why what Greg & Josh are suggesting couldn't
work - it's roughly what I had in mind anyway, except that we'd have
to use a URL rewrite on developer to get it to redirect requests to
wiki, as that hostname is used for other things so hijacking DNS
doesn't sound sensible.

-- 
Dave Page
EnterpriseDB UK Ltd: http://www.enterprisedb.com
PostgreSQL UK 2008 Conference: http://www.postgresql.org.uk




view thread (15+ messages)

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]
  Subject: Re: [HACKERS] Move the developers wiki?
  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