[Zope] Transferring Zope Settings

[jlegris]

Hi Andreas,

In this case, copying the Data.fs file isn't a feasible solution because
there is plenty of user content that would get over-written. The test
instance of course doesn't contain this data. I am pretty new to Zope, so
it's possible that I don't fully understand the development process when
using this tool, but I would find it surprising if there isn't a way to
administer updates without affecting content or manually replicating
configuration settings. Is this an inherent weakness of Zope?

Joel 

> -----Original Message-----
> From: Andreas Jung [mailto:lists at andreas-jung.com]
> Sent: Tuesday, June 14, 2005 12:32 AM
> To: jlegris; 'Andreas Jung'; zope at zope.org
> Subject: RE: [Zope] Transferring Zope Settings
> 
> You got the solution already : copy the Data.fs
> 
> -aj
> 
> --On 14. Juni 2005 00:27:25 -0700 jlegris <joel.legris at egadss.org> wrote:
> 
> > Wow, thanks for the quick response. I took this precaution while
> > customizing a Product that I was working on, but in this case I
> inherited
> > a system that was primarily customized through the ZMI. Is there any way
> > to transfer those settings?
> >
> > Joel
> >
> >> -----Original Message-----
> >> From: Andreas Jung [mailto:lists at andreas-jung.com]
> >> Sent: Tuesday, June 14, 2005 12:19 AM
> >> To: jlegris; zope at zope.org
> >> Subject: Re: [Zope] Transferring Zope Settings
> >>
> >>
> >>
> >> --On 14. Juni 2005 00:09:58 -0700 jlegris <joel.legris at egadss.org>
> wrote:
> >>
> >> > Hello All,
> >> >
> >> > I need to transfer Plone/Zope settings from a test instance to a live
> >> > instance of the Zope server. Aside from transferring the entire
> Data.fs
> >> > file or manually copying scripts and replicating configuration
> >> > settings, is there a simple way to do this?
> >>
> >> This way is simple if you think about your system setup before starting
> >> development. If you put your customization into a dedicated product and
> >> put
> >> this under revision control then you can easily keep track of change on
> >> test and production server.
> >>
> >> -aj
> 
>