Could you explain your publishing model?
-Original Message-
From: Robertson-Ravo, Neil (RX)
[mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 17, 2006 10:05 AM
To: CF-Talk
Subject: RE: SOT: Keeping Content In-Sync on QA and Production Sites
The whole sync scenario is one of the reasons we
The whole sync scenario is one of the reasons we are moving to a publishing
model - and away from CF itself for the main CMS system.
-Original Message-
From: Denny Valliant [mailto:[EMAIL PROTECTED]
Sent: 17 May 2006 01:09
To: CF-Talk
Subject: Re: SOT: Keeping Content In-Sync on QA
: SOT: Keeping Content In-Sync on QA and Production Sites
We allow dev and test to be modified as necessary. Code only goes to
production by syncing the entire site from test via RSync. Only a small
number of people can do the sync to prod.
We are looking at doing builds from a Subversion repo to
Thanks, Denny. These are some good issues to think about.
M!ke
-Original Message-
From: Denny Valliant [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 16, 2006 7:09 PM
To: CF-Talk
Subject: Re: SOT: Keeping Content In-Sync on QA and Production Sites
I like CMS's over Dreamw
We allow dev and test to be modified as necessary. Code only goes to
production by syncing the entire site from test via RSync. Only a
small number of people can do the sync to prod.
We are looking at doing builds from a Subversion repo to improve
record keeping regarding the changes to production
I like CMS's over Dreamweaver Templates, so I'm sorry to hear of the switch,
but the development in tiers is a way good idea.
While I have played with the idea of storing "content" in a SVN repository
or some such, generally when you talk of Dev / QA / Production you are
talking about code, vs. co
6 matches
Mail list logo
