[turba] how to simplify my turba upgrade process

[Robert P. J. Day]

On Tue, 1 Sep 2009, Michael Rubinsky wrote:

> Quoting "Robert P. J. Day" <rpjday at crashcourse.ca>:
>
> > 1) note the current set of addressbook tables in the horde
> > database (currently four of them)
> >
> > 2) following what i read in UPGRADING, run the appropriate scripts
> > to upgrade their schemas
>
> Only if they need to be updated. i.e if you are updating the
> sources.php file from the new *.dist version and plan to use the
> 'localsql' configuration. Otherwise, you just need to make sure you
> have appropriate maps in the entries.

  technically, i'm sure i don't *need* to nuke all that stuff, but i
don't know what kind of mess i've made of the turba install thus far
so, for the sake of cleanliness, i'd just like to simulate as if i was
starting from scratch, and was handed some old addressbooks from an
old turba install.  as in, i'd like to test what it would take if
someone told me, "here, here's some old addressbooks from a 2.0.5
install -- add turba 2.3.1 to our horde install and add those books
back in."

  in short, i want to install the latest turba, and bring the
addressbooks up to date to be compatible with the default, rather than
go the other way.  (and since i think i've already done those schema
upgrades, this would only make sense.)

> > 3) to start from scratch, delete *every* trace of turba from the
> > new horde install -- that is, the share tables, the install
> > directory ... *everything* except the addressbook tables
>
> Not sure why you would do this if your running the upgrade
> scripts...I don't see what version of Turba you are upgrading from,
> but if you have any share data this will obviously nuke it.

  as i mentioned above, going from turba 2.0.5 to 2.3.1.  and, yes, i
would be nuking the "share" stuff since i can always put it back in
later, right?  there's only four addressbooks and a half dozen users
(and i've got those share tables backed up) so i'm quite willing to
recreate that content since it won't take long.  (i'm still not sure
how the "share" stuff works, so i'll have to read up on that, anyway.)

> > 4) install the latest version of the turba tarball back under the
> > "horde" directory, and perform its standard configuration
> >
> > 5) do whatever it takes to configure the new turba, pointing it at
> > the existing addressbooks, figuring out how this "share" stuff
> > works while i'm at it.
> >
> > does that sound reasonable?  i'm being vague about that last step
> > since i'll get to that later.  but other than that, is my
> > *general* idea of how to add the addressbooks back into the new
> > horde install sane?  because if it is, i can at least start by
> > deleting all turba-related content (except for the existing
> > addressbooks) and re-installing, so i know i'm beginning with a
> > pristine install.
> >
> >  thoughts?  at the very worst, as long as i hang onto those
> > addressbooks, i can always start over if i somehow screw up.
>
> Except for my notes above, sounds like this should work.

  great, thanks.  i *think* i'm getting the hang of this.  of course,
i've thought that before.  back in a while after i get this process
started.

rday
--

========================================================================
Robert P. J. Day                               Waterloo, Ontario, CANADA

        Linux Consulting, Training and Annoying Kernel Pedantry.

Web page:                                          http://crashcourse.ca
Twitter:                                       http://twitter.com/rpjday
========================================================================