[Kroupware] Instructions for getting Horde working:
Diego Rivera
lrivera at racsa.co.cr
Wed May 7 11:47:21 CEST 2003
Ok....instructions for Horde.
There's a good "HOWTO" at http://www.geocities.com/oliversl/imp/
although it is for a slightly older version, and on RH7.2. Still, the
same principles apply (and the procedure is ALMOST 100% the same). You
may want to fall back on this for reference.
I've gotten this running on RHAS 2.1, updating the following packages:
apache-1.3.23-11.i386.rpm
curl-devel-7.9.5-2.i386.rpm
php-devel-4.1.2-7.i386.rpm
php-odbc-4.1.2-7.i386.rpm
apacheconf-0.8.2-2.noarch.rpm
mod_dav-1.0.3-5.i386.rpm
php-imap-4.1.2-7.i386.rpm
php-pgsql-4.1.2-7.i386.rpm
apache-devel-1.3.23-11.i386.rpm
mod_ssl-2.8.7-4.i386.rpm
php-ldap-4.1.2-7.i386.rpm
php-snmp-4.1.2-7.i386.rpm
apache-manual-1.3.23-11.i386.rpm
php-4.1.2-7.i386.rpm
php-manual-4.1.2-7.i386.rpm
curl-7.9.5-2.i386.rpm
php-dbg-4.1.2-7.i386.rpm
php-mysql-4.1.2-7.i386.rpm
The software requirements are listed on their site, so you want to check
there to be sure. Once you have Apache/PHP/MySQL working correctly
(with versions as required by the Horde project), you can proceed as
follows:
1) Download all the stuff (duh! ;) )
accounts-2.1.tar.gz forwards-2.2.tar.gz imp-3.2.1.tar.gz
mnemo-1.1.tar.gz passwd-2.2.tar.gz turba-1.2.tar.gz
chora-1.2.tar.gz horde-2.2.3.tar.gz kronolith-1.0.tar.gz
nag-1.1.tar.gz pear-1.0.1.1.tar.bz2 vacation-2.2.tar.gz
The Horde site (http://www.horde.org) has links to download these,
so go there and find the ftp links (http://ftp.horde.org/pub/). The ftp
site is split into project folders, so you'll have to go into each
folder and download the stuff you want. Also, inside each project
folder is a symlink called "<project-name>-latest.tar.gz". This is
obviously a link to the latest stable release for that particular
project. There's also RPMS/SRPMS there, but I haven't tried these and
thus don't recommend them (yet).
2) Extract the "horde" archive first. This will create the base horde
directory onto which all other projects need to be offloaded. I'll
refer to this as ${HORDE_HOME}. Subsequently, I'll refer to the home
directory for each project as ${<PROJECT>_HOME}. All of these homes
will be subdirectories of ${HORDE_HOME}. Note that ${HORDE_HOME}
initially includes the version (in this case, the name is horde-2.2.3) -
strip the version number out (horde-2.2.3 -> horde).
Also, the PEAR tarfile is NOT a project per-se, but it must be part of
the PHP include path. So extract the tarfile into a directory
accessible by the Apache server process, and add its location to the the
"include_path" directive in php.ini.
3) change into the newly created directory, and for each remaining
project, do as follows:
$ tar xzf "${PROJECT_TAR_FILE}"
This will create a bunch of subdirectories within the ${HORDE_HOME}
(all the aforementioned ${<PROJECT>_HOME}'s). However, these
directories will have versions attached to their names. Strip the
versions out such that the directory's name is as its project (i.e.,
rename "${HORDE_HOME}/imp-3.2.1" to "${HORDE_HOME}/imp").
4) Extract the encolsed tar file. It contains 3 files:
horde-fix.patch --> A few small bugfixes
horde-config.patch --> A basic configuration
horde-config.diff --> Same as the config patch, but with context
The idea here is to provide an index of what would need to be modified
for which setup. The context diff is provided for just that. For
example, it shows you where you should configure the MySQL account info
for the horde tables, etc.
You can apply the fix using:
$ cd ${HORDE_HOME} && patch -p1 < horde-fix.patch
You can also "preconfigure" Horde using:
$ cd ${HORDE_HOME} && patch -p1 < horde-config.patch
The patches must (should?) be run in that order.
Also, two scripts will be created with the config patch:
install-mysql.sh and rebuild-locales.sh
Their names should be self-explanatory. Edit them as you see fit for
your particular setup, keeping in mind the changes you make may affect
the configuration that you choose to use (for example, the password for
the mysql account).
You'll have to go through the diff to see where the configurations need
to be made. Refer to the aforementioned HOWTO for more pointers.
5) Once that's done, you may deploy it to your webserver as is by
copying (moving, whatever...) the ${HORDE_HOME} directory into your
document root.
6) You should run "http://yourhost:yourport/horde/test.php" to verify
the setup. It will let you know if you have any software compatiblity
problems.
7) Try it out, test the setup, and then customize further for your own
environment.
Note that these instructions are explicitly not comprehensive. This is
because I can't possibly predict the zillions of different setups out
there - I can only guide you using my experience to help.
If after this you still have trouble, follow the following procedure:
1) Read the howto mentioned at the top of this page
2) Read the FAQ's and docs at the horde website
3) Ask me the question! ;)
I'll be sure to help, but please try to read the docs beforehand as they
answer TONS of common questions.
The context diff should help a lot too.
Best
--
===========================================================
* Diego Rivera *
* *
* "The Disease: Windows, the cure: Linux" *
* *
* E-mail: lrivera<AT>racsa<DOT>co<DOT>cr *
* Replace: <AT>='@', <DOT>='.' *
* *
* GPG: BE59 5469 C696 C80D FF5C 5926 0B36 F8FF DA98 62AD *
* GPG Public Key avaliable at: http://pgp.mit.edu *
===========================================================
-------------- next part --------------
A non-text attachment was scrubbed...
Name: horde-config.tar.gz
Type: application/x-gzip
Size: 5042 bytes
Desc: not available
Url : http://mail.kde.org/pipermail/kroupware/attachments/20030507/26b2ac7e/horde-config.tar.bin
More information about the Kroupware
mailing list