|
|
Upgrading Horde and/or Horde Modules
This is specifically for a Solaris 8 install.
Errors or omissions, please mail to documentation@totkat.org.
Upgrading your Horde version needn't be a scary thing and can be tested concurrently with a live version still running. The webroot directive and symlinks are your friends while you test the newer version. I'll
explain how I upgraded from 2.0 to 2.2.1.
My live version was installed in $APACHEHOME/htdocs/horde-2.0
and the upgraded version in $APACHEHOME/htdocs/horde-2.2.1 while my apache docroot was $APACHEHOME/htdocs/horde
So, to swap between the two all I had to do was symlink $APACHEHOME/htdocs/horde to whichever version I
required. Now, on a large-scale production server, with real live users, that wouldn't be possible, so
you could install under $APACHEHOME/htdocs/horde/upgrade and simply point your browser at that for testing.
Whichever method you've chosen, you'd think you can symlink the modules from the live directory to the
test/upgrade one, but this causes problems in that within the configuration of the module code there
are relative references to the horde installation they're sitting under, so they would always reference
the one they were installed for. So, you actually do need to copy the whole of the modules to the relevant
location for the upgraded version, in my case $APACHEHOME/htdocs/horde/upgrade/$MODULENAME.
The only major, show-stopping issue I ran into by simply installing version 2.2.1 and configuring it as in the
configuration guide
was that from 2.0 to 2.2.1, the server name really does get pulled from what apache thinks it is with 2.2.1
Previously, under 2.0, I didn't need to set the server_name directive explicitly to the machine name but
with 2.2.1, unless I set it, horde uses the name apache gives it (in my case, the local name for the
machine when it is accessed from behind the firewall). Once I'd set that, things worked fine.
So, once you're happy that your new installation works, you can find a quiet 5 minutes in which you can
either put up a "Under maintenance, please come back in 5 minutes" page up in place of the usual horde index.php
on your old version, archive the old install and copy the new one into the relevant directory; or, if
you went with a symlink idea in some way, flip the link; or, frob the apache httpd.conf such that the
relevant docroot points to the new installation and restart apache.
Upgrading IMP
Upgrading IMP from 3.1 to 3.2.1 required nothing special at all. I didn't need to make any changes
to the configuration file, I just copied the 3.1 conf.php to the 3.2.1 config directory.
More details as I find time to write...
Mailto:webmaster@totkat.org
Site statistics
|
|
|
|
