Message-Id: <200509211257.j8LCvCDU040698@smtp-vbr5.xs4all.nl>
From: "Gevik babakhani" <gevik@xs4all.nl>
To: "'Magnus Hagander'" <mha@sollentuna.net>,
	"'Dave Page'" <dpage@vale-housing.co.uk>, <pgsql-www@postgresql.org>
Subject: Re: PGDN and CVS
Date: Wed, 21 Sep 2005 14:57:15 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
In-Reply-To: <6BCB9D8A16AC4241919521715F4D8BCE6C79CC@algol.sollentuna.se>
thread-index: AcW+kIcT6CwluUdAQASZMbpU/xojqAAAHbZAAAW3VSAAAOFiIA==

I have hacked with the current framework while ago. I almost know how things
work. (Dave has been a great help for my questions...).

My plan is to transfer the things I have created with drupal to the current
framework also :)

I was also thinking of letting everything in the site's database. Why would
we want to export things and then re-import them back in the CVS? But then
again this is just my opinion. The decisions are on the masters :)

Gevik


> -----Original Message-----
> From: Magnus Hagander [mailto:mha@sollentuna.net]
> Sent: Wednesday, September 21, 2005 2:32 PM
> To: Dave Page; Gevik babakhani; pgsql-www@postgresql.org
> Subject: RE: [pgsql-www] PGDN and CVS
> 
> > 	1.	Do we want to put the static PGDN files in CVS
> > anyway? Should we keep the PGDN files separate not mixing
> > with the current site's CVS?
> >
> >
> >
> > Yes, we do want them in CVS because we build the entire from
> > there & the backend database. we don't want to start pulling
> > in content from additional places as that just makes it much
> > harder to rebuild the servers if there is ever a problem.
> 
> While I agree with you in general, here's a point I'd liek to add. :-)
> 
> Gevik, if I get your latest blog post right, you are back to a custom
> CMS and not using Drupal? Then, IMHO, another option is if you can build
> the site completely with PHP code on our site framework and store all
> the data in the site database. In this case I see no more reason to
> store the static pages for this one than there is for the docs or other
> parts of the site. But this assumes that *all* the code required to
> maintain the site is in our framework, and we're not relying on an
> outside CMS.
> 
> //Magnus