[horde] Migrating to a new Horde install
simon.brereton at dada.net
Wed Mar 30 17:01:08 UTC 2011
> From: horde-bounces at lists.horde.org [mailto:horde-
> bounces at lists.horde.org] On Behalf Of Jan Schneider
> Zitat von Simon Brereton <simon.brereton at dada.net>:
> > -----Original Message-----
> >> From: horde-bounces at lists.horde.org [mailto:horde-
> >> bounces at lists.horde.org] On Behalf Of Jan Schneider Zitat von
> >> Brereton <simon.brereton at dada.net>:
> >> >> From: horde-bounces at lists.horde.org [mailto:horde-
> >> >> bounces at lists.horde.org] On Behalf Of Jan Schneider Zitat von
> >> Simon
> >> >> Brereton <simon.brereton at dada.net>:
> >> >>
> >> >> > So, after some success at getting installed, I'm stuck with
> >> >> most
> >> >> > obvious question. No one else has asked it, so it's probably
> >> >> stupid
> >> >> > or lazy..
> >> >> >
> >> >> > When Horde4.0 is finally released, many people will be
> >> >> from
> >> >> > a legacy installation. Which brings its own challenges, to
> >> >> > sure. However, I will be setting Horde4.0 on a completely
> >> box.
> >> >> > Given that there about 732 tabs worth of options to wade
> >> >> and
> >> >> > configure, is there some way to get an easy synopsis of all
> >> old
> >> >> > configuration parameters?
> >> >>
> >> >> Like the descriptions that come with each setting in the
> >> interface?
> >> >>
> >> >> You have two options: either you use Horde because of it's
> >> tremendous
> >> >> flexibility, one sign for that are "732" tabs of configuration.
> >> >> you hope the best that we picked sane defaults for each setting
> >> (we
> >> >> did).
> >> >> But please don't come back then to ask each time if this or
> >> >> feature would possible, until you've really gone through all
> >> >> configuration options.
> >> >
> >> > This may come as a shock - but I use Horde for both reasons.
> >> yes,
> >> > on the whole your defaults are very sane. However, I know I
> >> changed a
> >> > few - and it would be nice to know, or easily find which few, so
> >> can
> >> > work out if the change was sane, and whether to keep it like
> >> Are you saying that you changed some settings but don't remember
> >> which, and you are now asking for some tool to find that out for
> > I'd rather you didn't phrase it like that - but essentially yes.
> > I'm also assuming that a few options have (inevitably with total
> > refactoring like this) been added/removed/moved and I'd like to
> > doing a tab by tab comparison if possible..
> I thought you were kidding.
See the earlier reference to lazy/stupid..
> > Perhaps I'm missing something simple though..
> If you talk about upgrading, yes. If you save a configuration (and
> the configuration isn't saved immediately due to file permissions),
> you get a link to review a diff between the old and new configuration
> file. And of course you can make manual diffs between your old and
> your new installation. At least for conf.php, the configuration
> format didn't change from H3.
Well, that helps - so what you're saying is maybe the best way to do this (migration to a new box and update of H3) is...
pear channel-discover pear.horde.org
pear install horde/horde_role-beta
pear run-scripts horde/horde_role
pear list-files horde/horde
pear install --alldeps horde/horde-beta
pear install horde/imp-beta
pear install –alldeps horde/mnemo-beta
pear install horde/turba-beta
pear install horde/ingo-beta
go to the /usr/share/horde4/config/ directory of your Horde installation and copy conf.php.dist to conf.php:
cp /oldserver/usr/share/horde3/conf.php conf.php
copy the Horde3 DB (from the old server) to a new Horde4 DB
Go to the Admin interface and update the DB parameters.
Either `Update all DB schemas` or run `horde-db-migrate`
Although this warning from the UPGRADING says that this approach will not work..
Many configuration names and values have changed. It is suggested that you
start with a fresh configuration instead of trying to import some existing
configuration from Horde 3.
More information about the horde