Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: Re: PGDN and CVS
Date: Wed, 21 Sep 2005 14:01:50 +0100
Message-ID: 
 <E7F85A1B5FF8D44C8A1AF6885BC9A0E4CC2DCC@ratbert.vale-housing.co.uk>
Thread-Topic: [pgsql-www] PGDN and CVS
Thread-Index: AcW+kIcT6CwluUdAQASZMbpU/xojqAAAHbZAAAW3VSAAAOFiIAAAQG2Q
From: "Dave Page" <dpage@vale-housing.co.uk>
To: "Gevik babakhani" <gevik@xs4all.nl>,
	"Magnus Hagander" <mha@sollentuna.net>, <pgsql-www@postgresql.org>

=20

> -----Original Message-----
> From: Gevik babakhani [mailto:gevik@xs4all.nl]=20
> Sent: 21 September 2005 13:57
> To: 'Magnus Hagander'; Dave Page; pgsql-www@postgresql.org
> Subject: RE: [pgsql-www] PGDN and CVS
>=20
> I have hacked with the current framework while ago. I almost=20
> know how things
> work. (Dave has been a great help for my questions...).
>=20
> My plan is to transfer the things I have created with drupal=20
> to the current
> framework also :)
>=20
> I was also thinking of letting everything in the site's=20
> database. Why would
> we want to export things and then re-import them back in the=20
> CVS? But then
> again this is just my opinion. The decisions are on the masters :)

Database is fine with me as an alternative to CVS, just as long as it
can be generated out into a static format for replication to the
front-end servers.

What I don't want is something completely separate that requires
significant effort to keep synced up, or to recover in the event of a
disaster.

Regards, Dave