[horde] my plan for upgrading my horde install

[Robert P. J. Day]

On Tue, 25 Aug 2009, Andrew Morgan wrote:

> On Tue, 25 Aug 2009, Robert P. J. Day wrote:
>
> >  let me suggest a more refined approach to my 3.0.9 -> 3.3.4
> > upgrade. currently, there is a "horde" mysql database, with all of
> > the 3.0.9-related horde data.  let's leave that where it is, and
> > make a copy of it, call it "horde334" or something like that.
> > (what's the mysql command to just make a copy of an existing
> > database under a different name?  i guess i can look that up.)
> >
> >  once "horde334" exists, do all the upgrade steps on *that*, and i
> > should be able to do that with the collection of scripts that come
> > with horde-3.3.4.
> >
> >  once my horde334 database has been brought up to date, install
> > horde-3.3.4 and slowly and carefully configure it to resemble the
> > old setup, the main difference being that i obviously point it at
> > the "horde334" database, and i'm assuming it will use that
> > database, and not just blindly wipe it out and create a new, empty
> > one.
> >
> >  once that configuration is complete, i should be able to browse
> > to my new horde install and start work again, no?  is there
> > anything wrong with that logic?
>
> These are the steps I follow every time I upgrade Horde.  You don't
> need to install or use the intermediate versions of Horde.  Just
> follow all the instructions in the UPGRADING file.
>
> It sounds like you have an older version of Horde that does not
> support the version of PHP you have installed now, so a Horde
> upgrade will be required.  I remember running into a similar problem
> at some point myself.

  that's *exactly* the situation i'm in -- the massive debian upgrade
pushed me to PHP5, so i'm forced to upgrade the horde installation
similarly.

  as i read it, i can first upgrade the horde mysql database using the
upgrade scripts that come with horde-3.3.4.  i don't actually need to
*install* horde-3-3-4, i just need to un-tar it to get those upgrade
scripts, correct?  and run them, one at a time, on the database, until
it's up to date.

  and rather than upgrade the primary horde database itself, i'm going
to create a copy of it, and upgrade that copy so i can preserve the
original one, just in case.  (the old database is called "horde", so
i'll just call the copy "horde334" and let mysql look after both of
them.)

  once i have that upgraded "horde334" database, i'm going to install
horde-3.3.4 next to the original horde, configure it as similarly as
possible, then just point it at the "horde334" database.  i'm assuming
that's really all i'll need, correct?  this installation is really
being used for only two things:

  1) kronolith calendar, so i'll check the upgrade info on that as
     well

  2) a non-horde-based ticket system, which is already up to date,
     so that's pretty much done, i just need to link it back into the
     horde menus

and it's really only the ticket system that these folks care about, so
that makes this upgrade particularly easy -- that's the first thing i
can get running, while any horde apps can be re-installed slowly and
carefully.

  does all that sound reasonable?

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
========================================================================