That looks like the path of least resistance... the other option I was
considering to try out was to create backups of all the instance
specific neo*.xml files and then doing the whole copying larck and
restoring the XML files again. But I think your suggestion is probably
the safest!
Cheers
G
On Thu, 2 Sep 2004 11:48:57 -0400, Dave Watts <[EMAIL PROTECTED]> wrote:
> > I have just installed the CFMX updater and immediately
> > spotted that it only updates the default cfusion instance
> > when you are using the J2EE configuration option.
> >
> > I was wondering if anybody had figured out a best practice
> > for patching the other instances? The only thing I can think
> > of is to copy over the new instance folders in a similar
> > process to those described by Brandon in his article on
> > configuring multiple instances. Sadly this will wipe all
> > configuration information for that instance. I am a little
> > dubious about using a car file to back up the details as in
> > my experience this is far from a reliable method. Anybody
> > have any suggestions? Or ideas?
>
> You can rerun the updater and choose another instance, I think. Admittedly,
> this is kind of annoying to have to do this, but it's probably safer and
> easier in most cases than updating one instance and migrating files from
> that instance to other instances.
>
> Dave Watts, CTO, Fig Leaf Software
> http://www.figleaf.com/
> phone: 202-797-5496
> fax: 202-797-5444
>
>
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
