head	1.29;
access;
symbols
	HORDE_2_0_RC3:1.28.2.2
	HORDE_2_0:1.28.2.2
	HORDE_2_0_RC2:1.28
	HORDE_1_2_7:1.1.2.25
	RELENG_2:1.28.0.2
	HORDE_2_0_0_RC1:1.28
	HORDE_1_2_6:1.1.2.25
	HORDE_1_3_4:1.22
	HORDE_1_2_5:1.1.2.25
	HORDE_1_2_4:1.1.2.24
	HORDE_1_3_3:1.20
	HORDE_1_2_3:1.1.2.22
	HORDE_1_2_2:1.1.2.21
	HORDE_1_2_1:1.1.2.21
	HORDE_1_2_0:1.1.2.17
	HORDE_1_2_0_pre14:1.1.2.21
	HORDE_1_2_0_pre13:1.1.2.14
	HORDE_1_2_0_pre11:1.1.2.5
	HORDE_1_3_2:1.2
	HORDE_1_2_0_pre10:1.1.2.5
	HORDE_1_3_1:1.2
	HORDE_1_2_0_pre9:1.1.2.4
	HORDE_1_2_0_pre8:1.1.2.4
	HORDE_1_2_0_pre6:1.1.2.4
	horde-dev-20000104:1.2
	HORDE_1_2_0_pre5:1.1.2.3
	HORDE_1_2_0_pre4:1.1.2.1
	STABLE_1_2:1.1.0.2;
locks; strict;
comment	@# @;


1.29
date	2001.11.27.04.25.38;	author chuck;	state Exp;
branches;
next	1.28;

1.28
date	2001.10.14.12.04.03;	author jan;	state Exp;
branches
	1.28.2.1;
next	1.27;

1.27
date	2001.08.30.14.13.18;	author chuck;	state Exp;
branches;
next	1.26;

1.26
date	2001.08.28.13.08.53;	author jon;	state Exp;
branches;
next	1.25;

1.25
date	2001.08.26.17.26.49;	author chuck;	state Exp;
branches;
next	1.24;

1.24
date	2001.08.26.14.59.45;	author jon;	state Exp;
branches;
next	1.23;

1.23
date	2001.07.17.15.13.23;	author jon;	state Exp;
branches;
next	1.22;

1.22
date	2001.02.28.04.41.08;	author chuck;	state Exp;
branches;
next	1.21;

1.21
date	2001.02.07.12.15.03;	author bjn;	state Exp;
branches;
next	1.20;

1.20
date	2000.11.07.21.42.16;	author bjn;	state Exp;
branches;
next	1.19;

1.19
date	2000.11.07.21.10.08;	author bjn;	state Exp;
branches;
next	1.18;

1.18
date	2000.11.07.21.00.24;	author bjn;	state Exp;
branches;
next	1.17;

1.17
date	2000.11.07.20.38.27;	author bjn;	state Exp;
branches;
next	1.16;

1.16
date	2000.11.07.20.37.37;	author bjn;	state Exp;
branches;
next	1.15;

1.15
date	2000.11.01.21.38.26;	author bjn;	state Exp;
branches;
next	1.14;

1.14
date	2000.11.01.21.32.28;	author bjn;	state Exp;
branches;
next	1.13;

1.13
date	2000.11.01.21.22.05;	author bjn;	state Exp;
branches;
next	1.12;

1.12
date	2000.11.01.12.50.58;	author bjn;	state Exp;
branches;
next	1.11;

1.11
date	2000.10.18.19.43.43;	author bjn;	state Exp;
branches;
next	1.10;

1.10
date	2000.08.11.21.16.00;	author jon;	state Exp;
branches;
next	1.9;

1.9
date	2000.05.18.03.54.08;	author jon;	state Exp;
branches;
next	1.8;

1.8
date	2000.05.16.18.50.41;	author bjn;	state Exp;
branches;
next	1.7;

1.7
date	2000.05.02.15.17.15;	author chuck;	state Exp;
branches;
next	1.6;

1.6
date	2000.05.02.15.09.59;	author bjn;	state Exp;
branches;
next	1.5;

1.5
date	2000.05.02.14.42.13;	author bjn;	state Exp;
branches;
next	1.4;

1.4
date	2000.04.26.05.30.50;	author chuck;	state Exp;
branches;
next	1.3;

1.3
date	2000.03.09.16.21.29;	author jon;	state Exp;
branches;
next	1.2;

1.2
date	99.08.26.13.09.27;	author rkrusty;	state Exp;
branches;
next	1.1;

1.1
date	99.08.25.04.48.55;	author rkrusty;	state dead;
branches
	1.1.2.1;
next	;

1.1.2.1
date	99.08.25.04.48.55;	author rkrusty;	state Exp;
branches;
next	1.1.2.2;

1.1.2.2
date	99.10.19.15.28.51;	author rkrusty;	state Exp;
branches;
next	1.1.2.3;

1.1.2.3
date	99.10.19.15.39.25;	author rkrusty;	state Exp;
branches;
next	1.1.2.4;

1.1.2.4
date	99.12.28.02.32.32;	author jon;	state Exp;
branches;
next	1.1.2.5;

1.1.2.5
date	2000.01.27.16.22.38;	author jon;	state Exp;
branches;
next	1.1.2.6;

1.1.2.6
date	2000.04.09.22.07.07;	author chuck;	state Exp;
branches;
next	1.1.2.7;

1.1.2.7
date	2000.05.02.15.07.22;	author bjn;	state Exp;
branches;
next	1.1.2.8;

1.1.2.8
date	2000.05.12.21.05.56;	author bjn;	state Exp;
branches;
next	1.1.2.9;

1.1.2.9
date	2000.05.20.03.46.15;	author bjn;	state Exp;
branches;
next	1.1.2.10;

1.1.2.10
date	2000.05.22.21.33.34;	author chuck;	state Exp;
branches;
next	1.1.2.11;

1.1.2.11
date	2000.05.23.19.46.57;	author bjn;	state Exp;
branches;
next	1.1.2.12;

1.1.2.12
date	2000.05.23.20.03.18;	author bjn;	state Exp;
branches;
next	1.1.2.13;

1.1.2.13
date	2000.05.30.03.25.43;	author bjn;	state Exp;
branches;
next	1.1.2.14;

1.1.2.14
date	2000.05.30.21.38.06;	author bjn;	state Exp;
branches;
next	1.1.2.15;

1.1.2.15
date	2000.06.23.17.44.00;	author bjn;	state Exp;
branches;
next	1.1.2.16;

1.1.2.16
date	2000.06.27.14.59.47;	author bjn;	state Exp;
branches;
next	1.1.2.17;

1.1.2.17
date	2000.07.31.13.13.05;	author bjn;	state Exp;
branches;
next	1.1.2.18;

1.1.2.18
date	2000.08.22.15.20.50;	author jon;	state Exp;
branches;
next	1.1.2.19;

1.1.2.19
date	2000.08.22.15.34.37;	author jon;	state Exp;
branches;
next	1.1.2.20;

1.1.2.20
date	2000.08.22.16.49.15;	author bjn;	state Exp;
branches;
next	1.1.2.21;

1.1.2.21
date	2000.08.23.01.54.48;	author bjn;	state Exp;
branches;
next	1.1.2.22;

1.1.2.22
date	2000.09.19.14.53.09;	author bjn;	state Exp;
branches;
next	1.1.2.23;

1.1.2.23
date	2000.10.18.19.52.46;	author bjn;	state Exp;
branches;
next	1.1.2.24;

1.1.2.24
date	2000.10.26.18.52.59;	author bjn;	state Exp;
branches;
next	1.1.2.25;

1.1.2.25
date	2001.03.10.13.30.28;	author bjn;	state Exp;
branches;
next	;

1.28.2.1
date	2001.11.27.04.27.29;	author chuck;	state Exp;
branches;
next	1.28.2.2;

1.28.2.2
date	2001.12.03.16.21.17;	author chuck;	state Exp;
branches;
next	;


desc
@@


1.29
log
@I hate 'hordemgr'. Using 'horde' instead.
@
text
@Horde Installation Guide                                        docs/INSTALL
=--------------------------------------------------------------------------=

$Horde: horde/docs/INSTALL,v 1.28 2001/10/14 12:04:03 jan Exp $

Copyright 2000 Scott Martin <martin@@math.ohiou.edu>
Copyright 1998,1999 Charles J. Hagenbuch <chuck@@horde.org>
Copyright 1999 Ivan E. Moore II <rkrusty@@tdyc.com>
Copyright 1999 Mike Hardy <mikeh@@spark.com>
Copyright 1999 Jon Parise <parise@@pobox.com>

This code is licensed under the GNU Public License.
See the file COPYING in this directory.


----------------------
Requirements for Horde
======================

 * PHP 4, as recent a version as possible, with gettext enabled.
 * A web server, preferably an SSL web server so that Horde modules can
   use a secure connection.
 * A working session backend for PHP 4 sessions.


------------
Installation
============

Currently there is one way to configure Horde out of the box,
and that's manually.  If you install the IMP module as well, you
have a couple new options.  (Please see the INSTALL file that comes
with IMP for more information).

The following are notes from Scott Martin <martin@@math.ohiou.edu> on
how he successfully installed Horde/IMP.

I cleaned off my machine twice and did fresh installs of Red Hat Linux
7.0, PHP, Horde, IMP, Turba, etc. in order to write this document. I also
started with a minimal install. This document does not cover any installs
involving RPM's. I downloaded the source on each package and installed
from there. This is so those who don't have the ability to use RPM's can
still benefit from this document.

---------------------
Prerequisite Packages
=====================

The following are required to get PHP, Apache and the PHP extensions 
configured and made: autoconf, automake, bison, cvs, flex, gcc, libtool,
make and tar. Please make sure you have all of these programs installed
on your box before you proceed with this document.

In order to take full advantage of everything that Horde and IMP have to
offer, I have made a list of every package that they could possibly use
and a URL to obtain the latest release of each package. I suggest you
grab these packages before you go any further with the install process:


Web Servers
-----------

Apache - http://httpd.apache.org/

Secure Server: (This is optional. If you don't want secure <https>
    connections, leave it out.)

mod_ssl - http://www.modssl.org/
OpenSSL - http://www.openssl.org/  - This is a dependency for mod_ssl,
    but you may want to use it for LDAP also.


Scripting Languages
-------------------

PHP 4 - http://www.php.net/ - Don't download a package. You'll have to
    obtain the latest source code using CVS. Instructions below.


PHP Extensions
--------------

mm - http://www.engelschall.com/sw/mm/ - Shared memory library for both
    PHP and mod_ssl
IMAP - http://www.washington.edu/imap/ - Download the file called
    c-client.tar.Z
LDAP - http://www.openldap.org/
Berkeley DB - http://www.sleepycat.com/ - Required for LDBM in LDAP.
MySQL - http://www.mysql.com/ - Download the binaries for your OS. Not
    the source!
mcal - http://mcal.chek.com/ - Grab both libmcal file and mcaldrivers file.
FTP - (just include --enable-ftp command line on PHP configure)
gettext - http://www.gnu.org/software/gettext/gettext.html
XML - (PHP has XML libraries included. No need to install anything)
zlib - http://www.info-zip.org/pub/infozip/zlib/


External Binaries
-----------------

sendmail - http://www.sendmail.org/
ispell - http://fmg-www.cs.ucla.edu/fmg-members/geoff/ispell.html
    Note: No development has been done on ispell since 1995. Try:
aspell - http://aspell.sourceforge.net/ - A more intelligent ispell
pspell - http://pspell.sourceforge.net/ - Required if you install aspell
wvHtml - http://wvware.sourceforge.net/
png - http://www.libpng.org/pub/png/ - Required for wvHtml
ImageMagick - http://www.wizards.dupont.com/cristy/ImageMagick.html
    Required for wvHtml
freetype - http://www.freetype.org - Required for wvHtml
libwmf - http://wvware.sourceforge.net/libwmf.html - Required for wvHtml
xlHtml - http://www.xlhtml.org/
tar - (Hopefully this comes with your operating system)
GnuPG - http://www.gnupg.org/
RPM - http://www.rpm.org/
DPKG - http://www.debian.org/Packages/stable/base/dpkg.html
zipinfo -


--------------------------------
Installing Prerequisite Packages
================================

First off, I am installing all of these programs as user 'root' so as to
avoid authorization problems. Place all of the archives for the above
programs in one directory (I used /root).

Install these in any order you want. I'll do it in alphabetical order.


UW-IMAP c-client
----------------

"cd" to the directory containing your source files (I used /root):

cd /root

Untar the source file: tar -zxvf c-client.tar.Z

Rename the directory to imap. The name is too long! Type:

mv imap-2000.RELEASE-CANDIDATE.7 imap

"cd" to the imap directory: cd imap

Edit the "Makefile" file and find the proper port name for your operating
system. For most Linux installations it's "slx".

Type "make" followed by the proper port name: make slx


gettext
-------

"cd" to the directory containing your source files: cd ..

Untar the source file: tar -zxvf gettext*

"cd" the source directory: cd gettext*

Type the following commands:

./configure
make
make check
make install


libmcal and mcaldrivers
-----------------------

Make sure you grabbed both the libmcal and mcaldrivers archives from the
mcal website.

"cd" to the directory containing your source files: cd ..

Untar both files: tar -zxvf libmcal*
    tar -zxvf mcaldrivers*

"cd" to mcal-drivers directory: cd mcal-drivers

Move the mstore and icap directories inside of the libmcal directory:

mv * ../libmcal

Remove the mcal-drivers directory (it should be empty now):

cd ..
rm -frv mcal-drivers

"cd" to libmcal/mstore directory.

Type:

make

"cd" to libmcal/icap directory: cd ../icap

Type:

make

"cd" back to libmcal directory: cd ..

Change the permissions on the "configure" file. It's screwed up in the
distribution package:

chmod a+x configure

Type:

./configure --with-mstore --with-icap
make
make install

Create the local mstore directory:

mkdir /var/calendar

Set the permissions on the new directory:

chmod 1777 /var/calendar


libxml
------

"cd" to the directory containing your source files: cd ..

Untar the source: tar -zxvf libxml*

"cd" to libxml directory: cd libxml*

Type:

./configure
make
make install


mm (shared memory)
------------------

"cd" to the directory containing your source files: cd ..

Untar the source: tar -zxvf mm*

cd to the mm directory: cd mm*

Type:

./configure (Don't use --prefix= like they suggest in the INSTALL
    file. Let the package install in its default location. This will
    save problems later when compiling PHP and Apache.)
make
make install


MySQL
-----

NOTE: You are not required to use MySQL as your Horde/IMP database. PHP
also supports other databases such as PostgreSQL and Microsoft SQL. I
chose to use MySQL because it was the original database used by the Horde
project developers. If you successfully get another database working with
Horde/IMP, please submit the installation instructions for inclusion into
this document.

"cd" to the directory containing your source files: cd ..

Untar the source: tar -zxvf mysql*

Rename the newly created directory to "mysql": (Please note, that I used
    MySQL 3.23.25-beta during this install. The actual name of the
    directory you will rename may differ.)

mv mysql-3.23.25-beta-pc-linux-gnu-i686 mysql

Move the "mysql" directory to /usr/local : mv mysql /usr/local

Type the following commands:
groupadd mysql
useradd -g mysql mysql
cd /usr/local/mysql
scripts/mysql_install_db
chown -R mysql /usr/local/mysql
chgrp -R mysql /usr/local/mysql
bin/safe_mysqld --user=mysql &

Edit the file /etc/profile and add the mysql/bin path to it. Type:

pico /etc/profile  (or type: vi /etc/profile if you don't have pico)

Here is what my "path" line in the file looked like before editing:

PATH="$PATH:/usr/X11R6/bin"

and after:

PATH="$PATH:/usr/X11R6/bin:/usr/local/mysql/bin"

Save the file and exit the editor.

The following lines are for Red Hat Linux to provide automatic startup at
boot time for MySQL. Your operating system may differ:

cp support-files/mysql.server /etc/rc.d/init.d/mysqld
chmod a+x /etc/rc.d/init.d/mysqld
ln -s /etc/rc.d/init.d/mysqld /etc/rc.d/rc2.d/S90mysqld
ln -s /etc/rc.d/init.d/mysqld /etc/rc.d/rc3.d/S90mysqld
ln -s /etc/rc.d/init.d/mysqld /etc/rc.d/rc4.d/S90mysqld
ln -s /etc/rc.d/init.d/mysqld /etc/rc.d/rc5.d/S90mysqld


OpenLDAP
--------

"cd" to the directory containing your source files: cd ..

Untar the source: tar -zxvf openldap*

In order to get the source to compile with the default "./configure", we
have to install the LDBM backend first.

NOTE: You are not required to use Berkeley DB for your LDBM backend. There
are other programs which will work. I chose Berkeley DB because it is the
most commonly used LDBM backend. See the OpenLDAP installation
instructions for information on other backends that you can use.

"cd" to the directory containing your source files: cd ..

Untar the DB source: tar -zxvf db*

"cd" to the DB directory: cd db*

"cd" to the build_unix directory: cd build_unix

Type the following:

../dist/configure
make
make install

Note: If you want your LDAP to have SSL support, you need to go to the
section labeled "OpenSSL:" and install OpenSSL before you go any
further.

Now "cd" back to the openldap directory: cd /root/openldap*

If you installed Berkeley DB and OpenSSL your next commands will be:

CPPFLAGS="-I/usr/local/BerkeleyDB.3.1/include -I/usr/local/ssl/include" \
LDFLAGS="-L/usr/local/BerkeleyDB.3.1/lib -L/usr/local/ssl/lib" \
./configure
make depend
make
make install


OpenSSL
-------

"cd" to the directory containing your source files: cd ..

Untar the source: tar -zxvf openssl*

"cd" to the openssl directory: cd openssl*

Type the following:

./config
make
make test
make install


zlib
----

Note: My Red Hat Linux initial setup already had zlib installed. However,
if you are using Red Hat, you need to install the zlib-devel rpm also in
order for the zlib extension to build with PHP. I went ahead and
uninstalled the RPM's so I could build from source.

"cd" to the directory containing your source files: cd ..

Untar the zlib source: tar -zxvf zlib*

"cd" to the zlib directory: cd zlib

Type the following:

./configure
make
make install


Apache and PHP
--------------

"cd" to the directory containing your source files: cd ..

Untar Apache source: tar -zxvf apache*

Rename the apache source directory to "apache":

mv apache_1.3.14 apache

"cd" to the apache directory: cd apache*

Type:

./configure

This will setup enough of a preliminary configuration to allow you to
build PHP. We will come back and reconfigure apache again later.

"cd" back to the directory holding the archives: cd ..

Login to the PHP CVS repository. Use phpfi as the password. Type this
command:

cvs -d :pserver:cvsread@@cvs.php.net:/repository login

Obtain the PHP 4.0 CVS tree. Type these commands:

cvs -d :pserver:cvsread@@cvs.php.net:/repository co php4
cd php4

Login to the Zend CVS repository. Use zend as the password. Type this
command:

cvs -d :pserver:cvsread@@cvs.zend.com:/repository login

Obtain the Zend and TSRM (Thread Safe Resource Manager) CVS tree. Type
this command:

cvs -d :pserver:cvsread@@cvs.zend.com:/repository co Zend TSRM

Run "./buildconf" to generate the configure script.

Configure PHP. The following command will give you the proper support for
all of the programs we installed above, but I suggest you type
"./configure --help" and look over all of the options you can use:

./configure --with-zlib --with-mm --with-mysql=/usr/local/mysql \
--with-mcal=../libmcal --with-ldap --with-imap=../imap \
--with-gettext --enable-ftp --with-db3=/usr/local/BerkeleyDB.3.1 \
--with-apache=../apache

Now type:

make
make install

If you are NOT installing mod_ssl, skip this next section:

"cd" back to the directory the archives are stored in: cd ..

Untar the mod_ssl source: tar -zxvf mod_ssl*

"cd" to the mod_ssl directory: cd mod_ssl*

Type:

./configure --with-apache=../apache

If you are NOT installing mod_ssl, start again here:

cd ../apache

EAPI_MM=/usr/local ./configure \
--activate-module=src/modules/php4/libphp4.a \
--enable-module=ssl (Leave this line out if you are NOT installing mod_ssl.)

make
make certificate TYPE=custom  (Leave this line out if you are NOT
    installing mod_ssl)
make install
/usr/local/apache/bin/apachectl start  (or startssl for mod_ssl)
cp /usr/local/apache/bin/apachectl /etc/init.d/httpd
cd /etc/rc.d
ln -s ../init.d/httpd rc2.d/S99httpd
ln -s ../init.d/httpd rc3.d/S99httpd
ln -s ../init.d/httpd rc4.d/S99httpd
ln -s ../init.d/httpd rc5.d/S99httpd


----------------------------------
Installing Horde and IMP using CVS
==================================

Well, if you made it this far, your web server is up and running and so is
PHP. We need to grab the Horde and IMP packages from CVS. Let's get
started:

First, "cd" to the Apache web root. This is where we'll put the Horde and
IMP directories.

Type:

cd /usr/local/apache/htdocs
cvs -d :pserver:cvsread@@anoncvs.horde.org:/repository login

You will be asked for a password. Type: horde
then type:

cvs -z3 -d :pserver:cvsread@@anoncvs.horde.org:/repository co horde
cd horde
cvs -z3 -d :pserver:cvsread@@anoncvs.horde.org:/repository co imp
cvs -z3 -d :pserver:cvsread@@anoncvs.horde.org:/repository co turba
ln -s /usr/local/apache/htdocs/horde /horde
ln -s /usr/local/apache/htdocs/horde/imp /imp
ln -s /usr/local/apache/htdocs/horde/turba /turba

Now, we have the Horde, IMP and Turba source. Let's put our default
configuration files into place. Type:

cd /horde/config
cp horde.php.dist horde.php
cp mime.php.dist mime.php
cp registry.php.dist registry.php
cp html.php.dist html.php
cp modules.php.dist modules.php
cd /imp/config
cp conf.php.dist conf.php
cp prefs.php.dist prefs.php
cp html.php.dist html.php
cp servers.php.dist servers.php
cp mime.php.dist mime.php
cd /turba/config
cp conf.php.dist conf.php
cp html.php.dist html.php
cp sources.php.dist sources.php

Before we test horde, you need to edit httpd.conf in
/usr/local/apache/conf and uncomment the 4 'AddType' lines related to
PHP3 and PHP4. Also find the line that says:

DirectoryIndex index.html

and change it to say:

DirectoryIndex index.html index.php index.php3

Save the file and exit your editor.

You need to copy the file "php.ini-dist" which is in the directory where
you are storing the PHP CVS to "php.ini" in /usr/local/lib. For me, the
command was:

cp /root/php4/php.ini-dist /usr/local/lib/php.ini

Next, edit the php.ini file and change the line:

magic_quotes_gpc        =       On

To:

magic_quotes_gpc        =       Off


ln -s /usr/local/apache/htdocs/horde /horde
Also, change the following line
from:

include_path =  ; UNIX: "/path1:/path2"  Windows: "\path1;\path2"

To:

include_path = "/usr/local/lib/php"

Save the file and exit your editor, then type:

/etc/rc.d/init.d/httpd restart

This will restart the web server with the above changes and now you are
ready to test horde. Go to your web browser and point it to:

http://example.com/horde/test.php

Hopefully, your PHP setup passed all the required tests in test.php and
you are ready to move on to configuring Horde, IMP and Turba so you can
use them.


-----------------
External Binaries
=================

NOTE: You do not have to install the following items for Horde, IMP and
Turba to work. They are optional. These are the programs that IMP can use
to show attachments to your emails such as Microsoft Word documents,
Microsoft Excel documents, RPM packages, etc.


DPKG
----

Extremely simple to install! Download the binary package for your type of
system from ftp://ftp.debian.org/debian/project/dpkg/. For Red Hat, I
downloaded dpkg-1.6.15_i386.nondebbin.tar.gz.

Now, just switch to your root directory: cd /

Untar the archive: tar -zxvf /(archive_directory)/dpkg*.gz

That's it. It's installed!


GnuPG
-----

"cd" to the directory containing your source files (I used /root):

cd /root

Untar the source: tar -zxvf gnupg*

"cd" to the source directory: cd gnupg*

Type:

./configure
make
make check
make install
gpg --gen-key


aspell
------

"cd" to the directory containing your source files: cd ..

We have to install the required pspell library first:

Untar the source: tar -zxvf pspell*

"cd" to the source directory: cd pspell*

To install the library simply type

./configure
make
make install

Then install at least one pspell module. You can find more information
about available modules from the Pspell home page.

After all the pspell modules are installed

cd modules
./add-modules
cd ..
make
make install

Which will link in the pspell modules.

Now, to install aspell, "cd" back to the aspell source directory:

cd ..\aspell*

Type:

./configure
make
make install


ispell
------

This package is extremely old and I honestly cannot figure out how to
build it under Linux. I will update this section when I do. If you can
build it, please submit the installation instructions to me.


xlHtml
------

"cd" to the directory containing your source files: cd ..

Untar the source: tar -zxvf xlHtml*

"cd" to the source directory: cd xlHtml*

Type:

./configure
make
make check
make install


wvHtml
-------

"cd" to the directory containing your source files: cd ..

You have to install the prerequisites for wvHtml first. We'll start with
freetype:

NOTE: Do NOT install the version 2 Beta of freetype. They have changed
libttf to libfreetype which will cause libwmf to not find freetype.

Untar the truetype source: tar -zxvf freetype*

"cd" to the source directory: cd freetype*

Type :

./configure
make
make install

Now let's install libwmf.

Note: In my initial installation of Red Hat, I already had Xpm installed,
which is required for libwmf. However, libwmf also requires the Xpm header
files, which are in the rpm package XFree86-devel. I had to install this
package from the Red Hat CD-ROM. If you do not have this luxury, you will
have to install the XPM package from: ftp://ftp.x.org/contrib/libraries

"cd" back to the directory where the archives are stored: cd ..

Untar the souce: tar -zxvf libwmf*

"cd" to the libwmf directory:

Type:

./configure --with-ttf=/usr/local
make
make install

Next, we install libpng:

"cd" back to the directory where the archives are stored: cd ..

Untar the source: tar -zxvf libpng*

"cd" to the source directory: cd libpng*

You are probably going to have to read the installation instructions from
the distribution here, because you have to copy the proper "Makefile" from
the "scripts" directory to be able to install. I used "makefile.gcmmx".
Here are the commands I used to install:

cp scripts/makefile.gcmmx Makefile
make test
make install

Onward to ImageMagick install:

NOTE: I had problems getting the pre-compile binary packages to work
correctly, so I downloaded the source and built it. The following
instructions assume you are building from source:

"cd" back to the directory where the archives are stored: cd ..

Untar the source: tar -zxvf Image*

"cd" to the source directory: cd Image*

Type:

./configure --with-xpm=/usr/X11R6 --with-ttf=/usr/local \
--with-Magick=/usr/local
make
make install

Now install wvHtml:

Untar the source: tar -zxvf wv*

"cd" to the source directory: cd wv*

Type:

./configure --with-png=../libpng-<your version> --with-libwmf=../libwmf-<your
version> --with-Magick=../ImageMagick-<your version>
make
make install

--------------------------------------------------
Adding External Binaries To The IMP Configuration File
======================================================

Edit the conf.php file and add the paths to all of the external binaries
that we installed above:

cd /imp/config
pico conf.php (or use vi if you don't have the pine package installed)

Here is what the External Utilities section of IMP's conf.php looked like
after I made the changes:

/**
 ** External Utilities
 **/
$conf['utils']['spellchecker'] = '/usr/local/bin/aspell';
$conf['utils']['wordviewer'] = '/usr/local/bin/wvHtml';
$conf['utils']['excelviewer'] = '/usr/local/bin/xlHtml';
$conf['utils']['tar'] = '/bin/tar';
$conf['utils']['gpg'] = '/usr/bin/gpg';
$conf['utils']['rpm'] = '/bin/rpm';
$conf['utils']['dpkg'] = '/usr/bin/dpkg';
$conf['utils']['unzip'] = '/usr/bin/zipinfo';  # or: '/usr/bin/unzip -Z';


-----------------------------------------
Setting Up The Horde Database Under MySQL
=========================================

First of all, it is very important that you change the MySQL password for
the user 'root'. If you haven't done so already, type:

    mysqladmin [ -h <host> ] -u root -p password <new-password>

Login to MySQL by typing:

    mysql [ -h <host> ] -u root -p

Enter the password for root.

Now, create a database named "horde" and switch to it:

    mysql> create database horde;

    mysql> use horde;

Then set up the table called "horde_prefs". You can actually name it anything
you like as long as you use the same name when you alter the horde.php file.
Type:

    mysql> create table horde_prefs (pref_uid varchar(32) not null,
        pref_scope varchar(16) not null default '',
        pref_name varchar(32) not null, pref_value text null,
        primary key (pref_uid, pref_scope, pref_name));

This database schema is also available in horde/scripts/db/prefs.sql.

Next, create the user for the horde database. You can call this user any
name and give this user any password you want, just make sure that you
use the same name and password when you alter conf.php in /imp/config.
For this example, I will call the user "horde" and make the password
"hordepass". Type:

    mysql> use mysql;

    mysql> replace into user ( host, user, password )
        values ('localhost', 'horde', password('hordepass'));

    mysql> replace into db ( host, db, user, select_priv, insert_priv,
        update_priv, delete_priv, create_priv, drop_priv )
        values ('localhost', 'horde', 'horde', 'Y', 'Y',
        'Y', 'Y', 'Y', 'Y');

    mysql> flush privileges;

Exit MySQL by typing:

    mysql> quit

Now that MySQL is setup with the Horde database and the database user, we
can configure Horde to use MySQL. Edit horde.php in the /horde/config directory
with a text editor and make the following changes:

Change:

/**
 ** Preference System Settings
 **/
$conf['prefs']['driver'] = 'none';
$conf['prefs']['params'] = array();

To:

/**
 ** Preference System Settings
 **/
$conf['prefs']['driver'] = 'sql';
$conf['prefs']['params'] = array();
$conf['prefs']['params']['phptype'] = 'mysql';
$conf['prefs']['params']['hostspec'] = 'localhost';
$conf['prefs']['params']['username'] = 'user';
$conf['prefs']['params']['password'] = 'pass';
$conf['prefs']['params']['database'] = 'horde';
$conf['prefs']['params']['table'] = 'horde_prefs';



-----------------------
Getting Help with Horde
=======================

There is an online, user-editable FAQ at http://faq.horde.org/. Use it,
and add anything that you run into to it, so that others can benefit from
everything you figure out, and vice versa...

There is a web page for Horde at http://www.horde.org/. There are also
three mailing lists. One is the general IMP list, for feature requests,
bug questions, discussion, etc. It is imp@@lists.horde.org, and you can
subscribe by sending an emp ty email to imp-subscribe@@lists.horde.org.

The second list is the developers list at dev@@lists.horde.org, and it is
targeted at people who have serious feature requests or are trying to
extend or debug IMP and other Horde modules. You may subscribe to it by
sending an empty mail to dev-subscribe@@lists.horde.org.

The third list is the CVS list at cvs@@lists.horde.org, and most of the mail
on it is automatically generated announcements of changes to the CVS code.
Developers should definitely be on it, and anyone else who is curious
about the status of Horde development is welcome to join it by sending
email to cvs-subscribe@@lists.horde.org.

There are also web archives of all the mailing lists. For details:

    http://www.horde.org/mail/


------------
Found A Bug?
============

If you have found a bug you can add it to the Bugzilla bug system
we have setup for the Horde projects.  You can find it at:

    http://bugs.horde.org

Please verify that the bug is not already in the database and also
please be as descriptive as possible.  Fill out all the options.  You may
think it's something that affects everyone, but a lot of times it's 
specific to a browser or operating system.  So please be thorough.  In
the case of Bug Tracking, there is never too much information or
documentation.


-----------------------------------------------------------------------
We hope you find Horde useful and easy to use.  We thank you for taking
the time to try it and if you ever have any questions, just ask.

Enjoy,

The Horde Team
horde@@lists.horde.org
-----------------------------------------------------------------------
@


1.28
log
@Update wvHtml documentation

Submitted by: M Z Rahman <zrahman@@partex.net>
@
text
@d4 1
a4 1
$Horde: horde/docs/INSTALL,v 1.27 2001/08/30 14:13:18 chuck Exp $
d848 1
a848 1
For this example, I will call the user "hordemgr" and make the password
d854 1
a854 1
        values ('localhost', 'hordemgr', password('hordepass'));
d858 1
a858 1
        values ('localhost', 'horde', 'hordemgr', 'Y', 'Y',
@


1.28.2.1
log
@MFH: horde instead of hordemgr
@
text
@d4 1
a4 1
$Horde: horde/docs/INSTALL,v 1.28 2001/10/14 12:04:03 jan Exp $
d848 1
a848 1
For this example, I will call the user "horde" and make the password
d853 2
a854 2
    mysql> replace into user (host, user, password)
        values ('localhost', 'horde', password('hordepass'));
d856 3
a858 3
    mysql> replace into db (host, db, user, select_priv, insert_priv,
        update_priv, delete_priv, create_priv, drop_priv)
        values ('localhost', 'horde', 'horde', 'Y', 'Y',
@


1.28.2.2
log
@MFH 1.29: spacing
@
text
@d4 1
a4 1
$Horde: horde/docs/INSTALL,v 1.29 2001/11/27 04:25:38 chuck Exp $
d853 1
a853 1
    mysql> replace into user ( host, user, password )
d856 2
a857 2
    mysql> replace into db ( host, db, user, select_priv, insert_priv,
        update_priv, delete_priv, create_priv, drop_priv )
@


1.27
log
@remove references to mcrypt, since it's broken
@
text
@d4 1
a4 1
$Horde: horde/docs/INSTALL,v 1.26 2001/08/28 13:08:53 jon Exp $
d774 12
@


1.26
log
@Use the new anonymous CVSROOT.
@
text
@d4 1
a4 1
$Horde: horde/docs/INSTALL,v 1.25 2001/08/26 17:26:49 chuck Exp $
a88 1
mcrypt - http://mcrypt.hellug.gr/index.html - Download the libmcrypt file.
a224 16
libmcrypt
---------

"cd" to the directory containing your source files: cd ..

Untar the source: tar -zxvf libmcrypt*

"cd" to the libmcrypt directory: cd libmcrypt*

Type:

./configure --disable-posix-threads
make
make install


d449 1
a449 1
--with-apache=../apache --with-mcrypt
@


1.25
log
@fix link

Submitted by: Joseph Kacmarcik <joe@@chubbo.net>
@
text
@d4 1
a4 1
$Horde: horde/docs/INSTALL,v 1.24 2001/08/26 14:59:45 jon Exp $
d520 1
a520 1
cvs -d :pserver:cvsread@@cvs.horde.org:/cvs/horde login
d525 1
a525 1
cvs -z3 -d :pserver:cvsread@@cvs.horde.org:/cvs/horde co horde
d527 2
a528 2
cvs -z3 -d :pserver:cvsread@@cvs.horde.org:/cvs/horde co imp
cvs -z3 -d :pserver:cvsread@@cvs.horde.org:/cvs/horde co turba
@


1.24
log
@Update horde_prefs schema, add a pointer to horde/scripts/db/prefs.sql, and
change the link to the web-based archives.
@
text
@d4 1
a4 1
$Horde: horde/docs/INSTALL,v 1.23 2001/07/17 15:13:23 jon Exp $
d107 1
a107 1
wvHtml - http://www.wvware.org/
@


1.23
log
@Remove references to the 'connections' stuff and direct the user to
horde.php instead of conf.php for the preferences settings.
@
text
@d4 1
a4 1
$Horde: horde/docs/INSTALL,v 1.22 2001/02/28 04:41:08 chuck Exp $
d843 6
a848 3
    mysql> create table horde_prefs (uid varchar(32) not null,
        scope varchar(16) not null default '', pref_name varchar(32) not null,
        pref_value text null, primary key (uid, scope, pref_name));
d874 1
a874 1
with either the pico or vi editor and make the following changes:
d924 1
a924 1
There are also web archives of all the mailing lists. See:
d926 1
a926 1
    http://horde.tdyc.com                                    
@


1.22
log
@fix a couple of references to user_webmail_prefs, and update the prefs
schema whereever it's listed to match the horde_prefs schema. Also, show the
schema using varchar instead of char for field types; there aren't fixed
length fields so varchar is always better...
@
text
@d4 1
a4 1
$Horde: horde/docs/INSTALL,v 1.21 2001/02/07 12:15:03 bjn Exp $
d839 3
a841 4
Then set up the two tables called "horde_prefs" and
"connections". You can name these tables anything you like as long as you
use the same names when you alter the conf.php file in the /imp/config
directory (see instructions below). Type:
a846 4
    mysql> create table connections (addr varchar(8) not null,
        conn_id varchar(32) not null, conn_ts int(14) not null,
        primary key (addr, conn_id));

d870 1
a870 1
can configure IMP to use MySQL. Edit conf.php in the /imp/config directory
a894 23
Change:

/**
 ** Connection Tracking
 **/
$conf['connections']['track'] = false;
$conf['connections']['driver'] = 'sql';
$conf['connections']['params'] = array();

To:

/**
 ** Connection Tracking
 **/
$conf['connections']['track'] = true;
$conf['connections']['driver'] = 'sql';
$conf['connections']['params'] = array();
$conf['connections']['params']['phptype'] = 'mysql';
$conf['connections']['params']['hostspec'] = 'localhost';
$conf['connections']['params']['username'] = 'user';
$conf['connections']['params']['password'] = 'pass';
$conf['connections']['params']['database'] = 'horde';
$conf['connections']['params']['table'] = 'connections';
@


1.21
log
@Documentation fixes.

Submitted by: doug moore <lordscarlet@@idledreams.net>
@
text
@d4 1
a4 1
$Horde: horde/docs/INSTALL,v 1.20 2000/11/07 21:42:16 bjn Exp $
d839 1
a839 1
Then set up the two tables called "user_webmail_prefs" and
d844 3
a846 3
    mysql> create table user_webmail_prefs (uid char(32) not null,
        pref_name char(32) not null, pref_value text null,
        primary key (uid, pref_name));
d898 1
a898 1
$conf['prefs']['params']['table'] = 'user_webmail_prefs';
@


1.20
log
@'unzip -Z' is a synonym for 'zipinfo'.
@
text
@d4 1
a4 1
$Horde: horde/docs/INSTALL,v 1.19 2000/11/07 21:10:08 bjn Exp $
d457 2
d498 1
a498 1
cp /usr/local/apache/bin/apachectl /init.d/httpd
d547 1
@


1.19
log
@What 'unzip' really means is 'zipinfo'.
@
text
@d4 1
a4 1
$Horde: horde/docs/INSTALL,v 1.18 2000/11/07 21:00:24 bjn Exp $
d812 1
a812 1
$conf['utils']['unzip'] = '/usr/bin/zipinfo';
@


1.18
log
@Keep up with recent changes to IMP conf.php.
@
text
@d4 1
a4 1
$Horde: horde/docs/INSTALL,v 1.17 2000/11/07 20:38:27 bjn Exp $
d812 1
a812 1
$conf['utils']['unzip'] = '/usr/bin/unzip';
@


1.17
log
@...and don't forget to flush privileges.
@
text
@d4 1
a4 1
$Horde: horde/docs/INSTALL,v 1.16 2000/11/07 20:37:37 bjn Exp $
d802 3
a804 3
/* External Utilities */
$conf['utils'] = array();
$conf['utils']['sendmail'] = '/usr/sbin/sendmail';
d812 1
d877 3
a879 2
/* Preference System Settings */
$conf['prefs'] = array();
d885 3
a887 2
/* Preference System Settings */
$conf['prefs'] = array();
d899 3
a901 1
/* Connection Tracking */
d908 3
a910 1
/* Connection Tracking */
@


1.16
log
@MySQL setup clarifications/tidying.
@
text
@d4 1
a4 1
$Horde: horde/docs/INSTALL,v 1.15 2000/11/01 21:38:26 bjn Exp $
d856 2
a857 2
    mysql> REPLACE INTO user ( host, user, password )
        VALUES ('localhost', 'hordemgr', password('hordepass'));
d859 1
a859 1
    mysql> REPLACE INTO db ( host, db, user, select_priv, insert_priv,
d861 1
a861 1
        VALUES ('localhost', 'horde', 'hordemgr', 'Y', 'Y',
d863 2
@


1.15
log
@PHP must be built against c-client.
@
text
@d4 1
a4 1
$Horde: horde/docs/INSTALL,v 1.14 2000/11/01 21:32:28 bjn Exp $
d819 1
a819 2
the user 'root'. If you haven't done so already, log in as user 'root' and
type:
d821 1
a821 1
mysqladmin -p password (put your new password here)
d825 1
a825 1
mysql -p
d829 18
a846 9
Now, create the database name "horde" and set up the two tables called
"user_webmail_prefs" and "connections". You can name these fields anything
you like as long as you use the same names when you alter the conf.php
file in the /imp/config directory (see instructions below). Type:

create table user_webmail_prefs (uid char(32) not null, pref_name char(32)
not null, pref_value text null, primary key (uid, pref_name));
create table connections (addr varchar(8) not null, conn_id varchar(32)
not null, conn_ts int(14) not null, primary key (addr, conn_id));
d854 9
a862 5
REPLACE INTO user ( host, user, password )
VALUES ('localhost', 'hordemgr', password('hordepass'));
REPLACE INTO db ( host, db, user, select_priv, insert_priv, update_priv,
delete_priv, create_priv, drop_priv )
VALUES ('localhost', 'horde', 'hordemgr', 'Y', 'Y', 'Y', 'Y', 'Y', 'Y');
d866 1
a866 1
quit
@


1.14
log
@A few more caps and other pedants.
@
text
@d4 1
a4 1
$Horde: horde/docs/INSTALL,v 1.13 2000/11/01 21:22:05 bjn Exp $
a133 7

NOTE: You are not forced to use the UW-IMAP source as your IMAP client for
IMP. There are other programs available such as Cyrus IMAP that are
reported to work just as well. I chose UW-IMAP because it is the most
commonly used IMAP client. If you install another client and get it
successfully working, please submit the install instuctions for inclusion
into this document.
@


1.13
log
@1) Removed PostgreSQL, ODBC and MSSQL from prerequisites list, since I
didn't actually tell in the document how to install them.  See next note.

2) Added notes to the MySQL, UW-IMAP and Berkeley DB install sections
letting users know that there are alternatives to these programs if they
wish to use them.

3) Changed "ispell" reference in configuration file to "spellchecker".

4) Re-vamped "Adding External Binaries To The Configuration File" section.

5) Removed the Sablotron setup section and "--with-sablot" from
"./configure" statement of PHP section.

6) Finished writing up MySQL database and user setup instructions.

7) Removed all references to "rename" commands and replaced them with "cp"
commands.

8) Added MySQL path to /etc/profile in MySQL setup section.

Submitted by: Scott Martin <martin@@math.ohiou.edu>
@
text
@d4 1
a4 1
$Horde: horde/docs/INSTALL,v 1.12 2000/11/01 12:50:58 bjn Exp $
d52 1
a52 1
on your Linux box before you proceed with this document.
d69 2
a70 2
openssl - http://www.openssl.org/  - This is a dependency for mod_ssl,
    but you may want to use it for ldap also.
d107 1
a107 1
wvhtml - http://www.wvware.org/
d113 5
a117 5
xlhtml - http://www.xlhtml.org/
tar - (Hopefully this comes with your Linux installation)
gpg - http://www.gnupg.org/
rpm - http://www.rpm.org/
dpkg - http://www.debian.org/Packages/stable/base/dpkg.html
@


1.12
log
@New, more comprehensive install documentation.  This is quite a bit better
than what we had.  Also cleaned up tabbing, s/HORDE/Horde/, etc.

Submitted by: Scott Martin <martin@@math.ohiou.edu>
@
text
@d4 1
a4 1
$Horde$
d20 1
a20 1
 * PHP4, as recent a version as possible, with gettext enabled.
d23 1
a23 1
 * A working session backend for php4 sessions.
d38 6
a43 7
I cleaned off my machine and did a fresh install of Red Hat Linux 7.0 in
order to write this document. I also started with a minimal install. This
document does not cover any installs involving RPM's. I downloaded the
source on each package and installed from there. This is so those who
don't have the ability to use RPM's can still benefit from this
document.

d49 4
a52 4
The following are required to get PHP, Apache and Horde/IMP configured
and made: autoconf, automake, bison, cvs, flex, gcc, libtool, make and
tar. Please make sure you have all of these programs installed on your
Linux box before you proceed with this document.
d76 2
a77 1
php4 - http://www.php.net/
d84 1
a84 1
    php and mod_ssl
d88 1
a91 2
PostgreSQL - http://postgresql.readysetnet.com/ (Use either this or
    MySQL, not both)
a95 3
mssql - Microsoft SQL - commercial package
ODBC - http://www.odbc.org/
Sablotron - http://www.gingerall.com/
d135 14
a148 1
Untar the file: tar -zxvf c-client.tar.Z
a149 1
Rename the directory to imap. It's too long!:
d152 1
a152 1
"cd" to the imap directory.
d163 3
a165 1
Untar the file: tar -zxvf gettext*
d167 1
a167 1
"cd" the gettext directory: cd gettext*
d170 1
d183 3
a185 1
untar both files: tar -zxvf libmcal*
d188 1
a188 1
"cd" to mcal-drivers directory
d195 2
d201 3
a203 1
Type "make".
d207 3
a209 1
Type "make".
d224 5
a228 1
Create the local mstore directory: mkdir /var/calendar
d230 1
a230 1
Set the permissions on the new directory: chmod 1777 /var/calendar
d236 2
d243 1
d252 2
d259 1
d268 2
d271 1
d286 9
d297 3
a299 1
Rename the newly created directory "mysql":
d314 15
a328 1
The following lines are for RedHat Linux to provide automatic startup at
d342 2
d346 9
a354 3
If you want the source to compile with the default "./configure" you will
need a ldbm backend. I suggest Berkeley DB, available at
http://www.sleepycat.com/.
d363 1
d387 2
d390 1
d394 1
a400 14
Sablot
------

Untar the source: tar -zxvf Sablot*
"cd" to the Sablotron directory: cd Sablot*

Type the following commands: (Read the INSTALL document, so you'll know
    why you are typing these commands.)
cp bin/* /usr/bin
cp include/* /usr/include
cp lib/* /usr/lib
ldconfig


d406 6
a411 1
order for the zlib extension to build with PHP.
a412 1
Untar the zlib source source: tar -zxvf zlib*
d416 1
d425 2
d429 3
a431 1
Rename the apache source directory to "apache": mv apache_1.3.14 apache
d435 6
a440 3
Type "./configure" - This will setup enough of a preliminary
configuration to allow you to build PHP. We will come back and
reconfigure apache again later.
d450 1
d464 1
a464 1
Configure php. The following command will give you the proper support for
d468 4
a471 5
./configure --with-zlib --with-mm --with-sablot \
--with-mysql=/usr/local/mysql --with-mcal=../libmcal --with-ldap \
--with-imap=../im4ap --with-gettext --enable-ftp \
--with-db3=/usr/local/BerkeleyDB.3.1 --with-apache=../apache \
--with-mcrypt
d474 1
d478 1
a478 1
If you are not installing mod_ssl, skip this next section:
d487 1
d493 1
a495 1

a498 1

d502 1
a502 1
/usr/local/apache/bin/apachectl start
d542 5
a546 1
rename php.dist php *
d548 4
a551 1
rename php.dist php *
d553 3
a555 1
rename php.dist php *
d559 5
a563 2
PHP3 and PHP4. Also find the line that says "DirectoryIndex
index.html" and change it to say:
d583 4
a586 1
Also, change the following line from:
d594 1
a594 1
Save the file and exit you editor, then type:
d603 4
d614 2
a615 2
to show attachments to your emails such as Microsoft Word, Microsoft
Excel, and PKZipped archives.
d626 2
a627 1
and untar the archive: tar -zxvf /(archive_directory)/dpkg*.gz
d635 4
d655 3
a657 1
Install the required pspell library first.
d665 3
a667 3
    ./configure
    make
    make install
d674 5
a678 5
    cd modules
    ./add-modules
    cd ..
    make
    make install
d683 1
d697 2
a698 1
build it under Linux. I will update this section when I do.
d704 2
d721 3
a723 1
You have to install the prerequisites for wvHtml first. We'll start for
d741 1
a741 1
Note: In my initial installation of RedHat, I already had Xpm installed,
d744 1
a744 1
package from the RedHat CD-Rom. If you do not have this luxury, you will
d778 4
d797 5
a801 2
Adding External Binaries To IMP Configuration File
==================================================
d804 4
a807 1
pico conf.php
d812 1
a812 1
$conf['utils']['ispell'] = '/usr/local/bin/aspell';
d825 21
a845 1
For preferences:
d847 5
a851 6
create table user_webmail_prefs (
    uid             char(32) not null,
    pref_name       char(32) not null,
    pref_value      text null,
    primary key (uid, pref_name)
);
d853 22
a874 1
and in imp/config/conf.php
d887 1
a887 1
And for connection tracking:
d889 4
a892 6
create table connections (
    addr        varchar(8)  not null,
    conn_id     varchar(32) not null,
    conn_ts     int(14)     not null,
    primary key (addr, conn_id)
);
d894 1
a894 1
and in imp/config/conf.php
a905 14


Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 27 to server version: 3.23.25-beta

Type 'help;' or '\h' for help. Type '\c' to clear the buffer

mysql> GRANT ALL PRIVILEGES ON *.* TO hordemgr@@localhost
    -> IDENTIFIED BY 'hordemgr' WITH GRANT OPTION;
Query OK, 0 rows affected (0.00 sec)

mysql> GRANT ALL PRIVILEGES ON *.* TO hordemgr@@"%"
    -> IDENTIFIED BY 'hordemgr' WITH GRANT OPTION;
Query OK, 0 rows affected (0.00 sec)
@


1.11
log
@s/horde.org/lists.horde.org/ for mailing lists.
Repointed patches from support@@horde.org to dev@@lists.horde.org.
@
text
@d1 6
a6 1
HORDE Installation Guide
a14 1
Last Updated: 08/10/1999 
d16 2
a17 3

---------------------- 
Requirements for HORDE
a19 1

d21 2
a22 2
 * a web server, preferably an SSL web server so that HORDE Modules can use a 
   secure connection.
d26 141
a167 2
Methods of Installation
=======================
d169 480
d650 1
a650 4
         Currently there is one way to configure HORDE out of the box,
    and that's manually.  If you install the IMP module as well, you
    have a couple new options.  (Please see the INSTALL file that comes
    with IMP for more information).
d652 1
a652 2
	Making Necessary "httpd.conf" Changes:
	--------------------------------------
d654 3
a656 3
	(NOTE:  Older versions of Apache have DirectoryIndex in the srm.conf
	file, but Apache now recommends that all configuration directives be
	placed in httpd.conf)
d658 1
a658 1
	1) Add "index.php" to your "DirectoryIndex" line
d660 1
a660 3
-=-=-=-=
Manually
-=-=-=-=
d662 1
a662 1
          Here is the process for doing all of this by hand.
d664 1
a664 1
           1)  obtain horde*.tar.gz 
d666 4
a669 2
           2)  untar/gzip it into the directory you want. Move the
	       directory from "horde-1.2.xx" to "horde"
d671 3
a673 1
               You should now have a directory structure is like this:
d675 1
a675 10
                  horde/
                  horde/lib
                  horde/lib/src
                  horde/lib/src/...[lots of sub dir's]
                  horde/db
                  horde/config
                  horde/templates
                  horde/locale
                  horde/scripts
                  horde/docs
d677 1
a677 1
           3) In horde/config you will find a few files that you need to edit.
d679 1
a679 2
		The first file is "horde.php3.dist", and it needs the most work.
		Start by copying it to "horde.php3", then open it in an editor.
d681 1
a681 4
		Edit $default->horde_root_url, and set it to the part of the URL
		where Horde is installed, without the server name. For instance,
		If you want Horde at http://www.mikehardy.net/horde, you will
		say '/horde' here.
d683 1
a683 4
		If you would like to turn on our automated problem reporting
		page (users will be able to give you feedback), you should
		change $default->problem_reporting to "true;" and enter the
		email address to send reports to.
d685 4
a688 5
		Just as the problem reporting may be turned on, if you want
		to have automatic account signups you should change the value
		to "true;" and enter the correct email address, or implement
		a signup script in the skeleton we provide with
		<horde>/signup.php3
a689 3
           4) You now need to configure any modules you have installed. Please
              see their respective INSTALL files for more details.
          
d691 3
d695 2
d698 10
a707 3
-=-=-=-=
Packages
-=-=-=-=
d710 3
a712 5
                Currently there are 2 types packaging out there in use.
           (there are probably more but these are the ones I know of).
           They are:  RPM (RedHat Package Management) which has a 
           .rpm extension, and Debian Package format which  has a .deb
           extension.
d714 1
a714 8
               There is currently a Debian package being maintained by Ivan  
           Moore II.  It is available from http://snowcrash.tdyc.com/debian.php3
           and is also available within the Debian distribution.  This
           package takes care of most configuration issues and still allows you
           to customize your HORDE installation. This package also detects 
           Postgres and MySql installations and will automagically configure
           either for use with HORDE. After installing this package you will
           have a functional HORDE installation.
d716 6
a721 2
		There are also RPM packages maintained by Dale Lovelace 
	   <dale@@redhat.com>. They are available from http://ftp.horde.org/
d723 1
d725 10
d736 1
d738 6
a743 3
-=-=-=-=-=-=-
Special Notes
-=-=-=-=-=-=-
d745 1
d747 10
a756 1
===== Putting Horde as Apache's web-root ==========
a757 3
A lot of people would like to have Horde be Apache's web-root, so that they
can simply specify a server and not have to type anything else in. If you
want to do this, you need to add these lines to your httpd.conf:
d759 2
a760 4
===Start===
DocumentRoot /home/httpd/htdocs/horde/
Alias /horde/ /home/httpd/htdocs/horde/
===End===
d762 1
a762 2
Where "/home/httpd/htdocs/horde/" is where ever you have installed the
Horde package (with IMP under it).
d764 3
a766 3
Note that these lines are probably already in your httpd.conf somewhere,
and it might be best to just modify them, or add them individually in the
location the other references to "DocumentRoot" and "Alias" are.
d768 3
d774 1
a774 1
Getting Help with HORDE
a776 1

d781 1
a781 1
There is a web page for HORDE at http://web.horde.org/. There are also
d794 1
a794 1
about the status of HORDE development is welcome to join it by sending
a797 1
  http://horde.tdyc.com                                    
d799 4
a802 1
=-=-=-=-=-=-
d804 1
a804 1
=-=-=-=-=-=-
d806 2
a807 2
    If you have found a bug you can add it to the Bugzilla bug system
we have setup for the HORDE projects.  You can find it at:
d809 1
a809 1
http://bugs.horde.org
d811 1
a811 1
    Please verify that the bug is not already in the database and also
d819 2
a820 3

----------------------------------------------------------------------
We hope you find HORDE useful and easy to use.  We thank you for taking
d827 1
a827 1
----------------------------------------------------------------------
@


1.10
log
@Note that we required gettext.
@
text
@d156 2
a157 2
bug questio ns, discussion, etc. It is imp@@horde.org, and you can
subscribe by sending an emp ty email to imp-subscribe@@horde.org.
d159 1
a159 1
The second list is the developers list at dev@@horde.org, and it is
d162 1
a162 1
sending an empty mail to dev-subscribe@@horde.org
d164 2
a165 2
The third list is the CVS list at cvs@@horde.org, and most of the mail on
it is automatically generated announcements of changes to the CVS code.
d168 1
a168 1
email to cvs-subscribe@@horde.org.
d198 1
a198 1
horde@@horde.org
@


1.9
log
@Removed the rest of the locale/ stuff, including buildLang.sh.
@
text
@d18 1
a18 1
 * PHP4, as recent a version as possible.
@


1.8
log
@Add the buildLang.sh step to the instructions (for now).
@
text
@d88 1
a88 4
           4) cd to horde/locale and run buildLang.sh to build the language
              files.  (This step will be deprecated in the near future.)

           5) You now need to configure any modules you have installed. Please
@


1.7
log
@PHPLIB is no longer needed.
DATABASE was specific to phplib; I think we should just re-write it from
         scratch once we have a concrete idea of db use in the post-phplib
	 world.
INSTALL is updated to reflect that php4 is required, and you don't need
        phplib anymore.
@
text
@d88 2
d91 1
a91 1
           4) You now need to configure any modules you have installed. Please
@


1.6
log
@(1)  As of Apache 1.3.6, access.conf and srm.conf are deprecated; reflect
this change of philosophy in the install docs.

(2)  "index.php3" should be "index.php" for PHP4.
@
text
@d18 1
a18 1
 * php 3.0.12 or greater 
d20 2
a21 4
     secure connection.
 * PHPLib 7 or greater
 * MySQL installed and configured so your webserver can access it (or a 
	willingness to try shared memory in PHPLib)
a33 50
	     Either way, you will have to install PHPLib first, and that's
	a manual process.

-=-=-=
PHPLib
-=-=-=

	     These instructions are not comprehensive, and may not be *exactly*
	what you want for your site. They are known to work on a clean system
	for getting Horde and IMP running though. If you want to go beyond
	that, you will need to consult the PHPLib documentation for more
	detailed instructions.


	Installing the Files:
	---------------------

	1) Download PHPLib from http://phplib.netuse.de/
	2) Unpack PHPLib in your desired installation location
	3) Go to the parent of your webserver's DocumentRoot 
		(e.g. "/home/httpd")
	4) Create a "php" directory (e.g. "/home/httpd/php")
	5) Copy the contents of the PHPLib distributions "php" directory
		into the "php" directory you created in your DocumentRoot.
	6) Copy the contents of the <horde>/phplib/ directory to your
		new "php" directory next to your DocumentRoot
	7) Rename the file "horde_phplib.inc" to "local.inc". (NOTE: if you
		already have PHPLib applications, append the contents of 
		the horde_phplib file to the local.inc file or
		you will lose your old PHPLib application settings)
	8) Edit the new "local.inc" file, and follow its directions.
		The gist of it is that you will have to uncomment the
		section of the file that applies to your PHP storage
		system, with databases being standard, and shared memory
		(SHM) as well as LDAP needing testing.

		NOTE: for shared memory to work, it must be built into PHP.
	    The 3.0.12 PHP RPMs shipped with RedHat 6.1 did not have this.
            Shared memory is only available on Linux and Solaris.


	Making Necessary "php.ini" Changes:
	-----------------------------------

	1) Add the new "php" directory to your "include_path" in your php.ini
	2) Add the "prepend.php3" file in that php directory to the
		"auto_prepend_file" line in your php.ini
	3) Enable magic_quotes_gpc (change them to "On") in your php.ini


a41 12


	Database Changes
	----------------

	If you're using a database (like MySQL in this example), you'll
	need to do these two things:

	1) You'll need to create a "horde" database
	2) You'll need to execute the file create_database.mysql from
		the PHPLib-7 distribution against the "horde" database
		(or the file for your database if its different)
@


1.5
log
@I realize the phplib section will soon be gone... but until then:  clarify
that it's older (3.0.12) RedHat PHP RPMs that don't have shared mem support.
The Horde-customized 3.0.16 ones have it.
@
text
@d86 2
a87 2
	Making Necessary "access.conf"/"httpd.conf" Changes:
	----------------------------------------------------
d89 5
a93 1
	1) Add "index.php3" to your "DirectoryIndex" line
@


1.4
log
@url tweak until we get rid of phplib
@
text
@d73 1
a73 1
			At least in RedHat's packages, this is not the case.
@


1.3
log
@Removing build.pl references from the documentation.
@
text
@d53 1
a53 1
	1) Download PHPLib from http://phplib.de
@


1.2
log
@[IEM] moving installation and support docs into docs/ subdir to clean
up main tree a bit more. (leaving COPYING and README which points to the
docs dir)
@
text
@d127 1
a127 7
           3) go into horde/lib/src and run the following command:

                  ./build.pl --help

			It will display usage instructions.

           4) In horde/config you will find a few files that you need to edit.
d149 1
a149 1
           5) You now need to configure any modules you have installed. Please
@


1.1
log
@file INSTALL was initially added on branch STABLE_1_2.
@
text
@d1 266
@


1.1.2.1
log
@[IEM] migrating all core documentaiton (except readme and copying) into
the docs/ sub directory
@
text
@a0 353
HORDE Installation Guide
Copyright 1998,1999 Charles J. Hagenbuch <chuck@@horde.org>
Copyright 1999 Ivan E. Moore II <rkrusty@@tdyc.com>
Copyright 1999 Mike Hardy <mikeh@@spark.com>
Copyright 1999 Jon Parise <parise@@pobox.com>

This code is licensed under the GNU Public License.
See the file COPYING in this directory.

Last Updated: 08/25/1999 [IEM]


---------------------- 
Requirements for HORDE
======================


 * php 3.0.12 or greater 
 * a web server, preferably an SSL web server so that HORDE Modules can use a 
     secure connection.
 * PHPLib 7 or greater
 * Database supported by phplib (MySql or Postgresql definatly work)
     (or a willingness to try shared memory in PHPLib)


-----------------------
Methods of Installation
=======================

          There are several ways to install and configure HORDE.  The first
       way is via a package.  There are both Debian and RedHat packages
       for HORDE available.  You can find them either from ftp://ftp.horde.org
       or http://horde.tdyc.com 

           The second method is manually.  Below are the steps required to
       get HORDE installed and functioning on your system.



-=-=-=
PHPLib
-=-=-=

             Horde requires PHPLib.  Though you should follow the instructions
        that come with PHPLib for installing and setting it up, there are
        some Horde specifics that we need to address.

	     These instructions are not comprehensive, and may not be *exactly*
	what you want for your site. They are known to work on a clean system
	for getting Horde running though. If you want to go beyond
	that, you will need to consult the PHPLib documentation for more
	detailed instructions.


	Installing the Files:
	---------------------

	1) Download PHPLib from http://phplib.de
	2) Unpack PHPLib in your desired installation location
	3) Go to the parent of your webserver's DocumentRoot 
		(e.g. "/home/httpd")
	4) Create a "php" directory (e.g. "/home/httpd/php")
	5) Copy the contents of the PHPLib distributions "php" directory
		into the "php" directory you created in your DocumentRoot.
	6) Copy the contents of the <horde>/phplib/ directory to your
		new "php" directory next to your DocumentRoot
	7) Rename the file "horde_phplib.inc" to "local.inc". (NOTE: if you
		already have PHPLib applications, append the contents of 
		the horde_phplib file to the local.inc file or
		you will lose your old PHPLib application settings)
	8) Edit the new "local.inc" file, and follow its directions.
		The gist of it is that you will have to uncomment the
		section of the file that applies to your PHP storage
		system, with databases being standard, and shared memory
		(SHM) as well as LDAP needing testing.

		NOTE: for shared memory to work, it must be built into PHP.
			At least in RedHat's packages, this is not the case.
            Shared memory is only available on Linux and Solaris.

        *** NOTE ***
 
              If you plan on using shared memory or any other non-sql
           container you will need to make sure you include the proper
           phplib include file in your prepend.php3 file

                    Shared Memory = ct_shm.inc 
                    LDAP          = ct_ldap.inc
                    DBM           = ct_dbm.inc
                    SQL           = ct_sql.inc
              
                There may already be a line requiring 'ct_sql.inc'.  All
           you need to do is replace ct_sql.inc with the include file that
           matches your container choice from above.


	Making Necessary "php.ini" Changes:
	-----------------------------------

        These commands can also be added on a per directory bases.  See
        the Apache section further down for more information.

	1) Add the new "php" directory to your "include_path" in your php.ini
	2) Add the "prepend.php3" file in that php directory to the
		"auto_prepend_file" line in your php.ini
	3) Disable magic_quotes_gpc (change them to "Off") in your php.ini
        

	Making Necessary "access.conf"/"httpd.conf" Changes:
	----------------------------------------------------

	1) Add "index.php3" to your "DirectoryIndex" line


	Database Changes
	----------------

        Please see the DATABASE file for help with configuring your
        HORDE database.

-=-=-
Horde 
-=-=-

          Now for Horde itself.

           1)  obtain horde*.tar.gz 

           2)  untar/gzip it into the directory you want. Move the
	       directory from "horde-1.2.xx" to "horde"

               You should now have a directory structure is like this:

                  horde/
                  horde/lib
                  horde/lib/src
                  horde/lib/src/...[lots of sub dir's]
                  horde/db
                  horde/config
                  horde/config/scripts   [where sql scripts are]
                  horde/templates
                  horde/locale
                  horde/scripts
                  horde/docs

           3) go into horde/lib/src and run the following command:

                  ./build.pl --help

			It will display usage instructions.

           4) In horde/config you will find a few files that you need to edit.

		The first file is "horde.php3.dist", and it needs the most work.
		Start by copying it to "horde.php3", then open it in an editor.

		Edit $default->horde_root_url, and set it to the part of the URL
		where Horde is installed, without the server name. For instance,
		If you want Horde at http://www.mikehardy.net/horde, you will
		say '/horde' here.

		If you would like to turn on our automated problem reporting
		page (users will be able to give you feedback), you should
		change $default->problem_reporting to "true;" and enter the
		email address to send reports to.

		Just as the problem reporting may be turned on, if you want
		to have automatic account signups you should change the value
		to "true;" and enter the correct email address, or implement
		a signup script in the skeleton we provide with
		<horde>/signup.php3


           5) You now need to configure any modules you have installed. Please
              see their respective INSTALL files for more details.
          



-=-=-=-=
Packages
-=-=-=-=


                Currently there are 2 types packaging out there in use.
           (there are probably more but these are the ones I know of).
           They are:  RPM (RedHat Package Management) which has a 
           .rpm extension, and Debian Package format which  has a .deb
           extension.

               There is currently a Debian package being maintained by Ivan  
           Moore II.  It is available from http://horde.tdyc.com/
           and is also available within the Debian distribution.  This
           package takes care of most configuration issues and still allows you
           to customize your HORDE installation. This package also detects 
           Postgres and MySql installations and will automagically configure
           either for use with HORDE. After installing this package you will
           have a functional HORDE installation.

		There are also RPM packages maintained by Dale Lovelace 
	   <dale@@redhat.com>. They are available from http://ftp.horde.org/




-=-=-=-=-=-=-
Special Notes
-=-=-=-=-=-=-


===== Putting Horde as Apache's web-root ==========

A lot of people would like to have Horde be Apache's web-root, so that they
can simply specify a server and not have to type anything else in. If you
want to do this, you need to add these lines to your httpd.conf:

===Start===
DocumentRoot /home/httpd/htdocs/horde/
Alias /horde/ /home/httpd/htdocs/horde/
===End===

Where "/home/httpd/htdocs/horde/" is where ever you have installed the
Horde package (with IMP under it).

Note that these lines are probably already in your httpd.conf somewhere,
and it might be best to just modify them, or add them individually in the
location the other references to "DocumentRoot" and "Alias" are.

====== Using Apache's config files to handle phplib prepends ========

# Added for HORDE   
<Directory /usr/share/horde>  
Options Indexes FollowSymLinks
AllowOverride None
order allow,deny
allow from all
php3_include_path /etc/horde:/usr/lib/phplib
php3_auto_prepend_file /etc/horde/prepend.php3
php3_magic_quotes_gpc Off
</Directory>


Adding something like the above to either Apaches httpd.conf or access.conf
(it doesn't seem to matter which conf file it goes in anymore) will allow
per directory loading of the required phplib files.  Otherwise if you throw
the prepend line into your php3.ini file, these files will be loaded for
every page that is loaded on your server which could be bad if one of the
phplib files were to get hosed.  Doing the above limits your possible problems
due to a mistake or bad php or whatever to just your horde web tree.

To explain the above I'll break it down.

The first 4 lines:

  Options Indexes FollowSymLinks
  AllowOverride None
  order allow,deny
  allow from all

are normal Apache settings.  You can change them to whatever you want, I just
used the defaults.

The next 3 lines are what we need for things to work:

php3_include_path /etc/horde:/usr/lib/phplib
php3_auto_prepend_file /etc/horde/prepend.php3
php3_magic_quotes_gpc Off

the include path will have both your phplib include path, ie..where your
core phplib files are, and the path to where you placed your horde phplib
files.  The default location is in horde/phplib but for a Debian install,
which is where the above lines are from, I moved all the horde config
files into /etc/horde.  These included the files out of horde/phplib.

So your configuration may look something like this: 
  
(for this example let's say your web tree is /home/httpd/html and your
phplib files are storged in /home/httpd/phplib and your horde files are
in /home/httpd/html/horde.  And let's say you left your horde phplib files
where they were, in /home/httpd/html/horde/phplib)

Your Directory config would look like this:

<Directory /home/httpd/html/horde>
Options Indexes FollowSymLinks
AllowOverride None
order allow,deny
allow from all
php3_include_path /home/httpd/html/horde:/home/httpd/phplib
php3_auto_prepend_file /home/httpd/phplib/prepend.php3
php3_magic_quotes_gpc Off
</Directory>


Now keep in mind you really need to read the README in the phplib directory
of horde as there are some things you need to take care of in that prepend 
file.  

-----------------------
Getting Help with HORDE
=======================


There is an online, user-editable FAQ at http://faq.horde.org/. Use it,
and add anything that you run into to it, so that others can benefit from
everything you figure out, and vice versa...

There is a web page for HORDE at http://web.horde.org/. There are also
three mailing lists. One is the general IMP list, for feature requests,
bug questio ns, discussion, etc. It is imp@@horde.org, and you can
subscribe by sending an emp ty email to imp-subscribe@@horde.org.

The second list is the developers list at dev@@horde.org, and it is
targeted at people who have serious feature requests or are trying to
extend or debug IMP and other Horde modules. You may subscribe to it by
sending an empty mail to dev-subscribe@@horde.org

The third list is the CVS list at cvs@@horde.org, and most of the mail on
it is automatically generated announcements of changes to the CVS code.
Developers should definitely be on it, and anyone else who is curious
about the status of HORDE development is welcome to join it by sending
email to cvs-subscribe@@horde.org.

There are also web archives of all the mailing lists. See:
  http://horde.tdyc.com                                    

=-=-=-=-=-=-
Found A Bug?
=-=-=-=-=-=-

    If you have found a bug you can add it to the Bugzilla bug system
we have setup for the HORDE projects.  You can find it at:

http://bugs.horde.org

    Please verify that the bug is not already in the database and also
please be as descriptive as possible.  Fill out all the options.  You may
think it's something that affects everyone, but a lot of times it's 
specific to a browser or operating system.  So please be thorough.  In
the case of Bug Tracking, there is never too much information or
documentation.



----------------------------------------------------------------------
We hope you find HORDE useful and easy to use.  We thank you for taking
the time to try it and if you ever have any questions, just ask.

Enjoy,

The Horde Team
dev@@horde.org
---------------------------------------------------------------------
@


1.1.2.2
log
@[IEM] minor fixes in wording
@
text
@d10 1
a10 1
Last Updated: 10/19/1999 [IEM]
d39 1
d129 2
a130 3
           2)  untar/gzip it into the directory you want under your
               web tree. Move the directory from
	       "horde-1.2.xx" to "horde"
d177 27
@


1.1.2.3
log
@[IEM] fixing some wording in the phplib instruction portion
@
text
@d205 1
a205 1
<Directory /home/httpd/htdocs/horde>  
d210 2
a211 2
php3_include_path /usr/lib/phplib
php3_auto_prepend_file /usr/lib/phplib/prepend.php3
d238 2
a239 2
php3_include_path /usr/lib/phplib
php3_auto_prepend_file /usr/lib/phplib/prepend.php3
d244 3
a246 1
files.  
@


1.1.2.4
log
@Correct the location of COPYING
@
text
@d8 1
a8 1
See the file COPYING in the main directory.
@


1.1.2.5
log
@We only support phplib 7.0 and 7.3 (currently).
@
text
@d21 1
a21 1
 * phplib 7.0 or phplib 7.3
@


1.1.2.6
log
@More documentation updates
@
text
@d2 1
a2 1
Copyright 1998,1999,2000 Charles J. Hagenbuch <chuck@@horde.org>
d21 2
a22 2
 * phplib, included with the horde distribution
 * Database supported by phplib (MySql or Postgresql definitely work)
d31 2
a32 2
       way is via a package. There are both Debian and RedHat packages
       for HORDE available. You can find them either from ftp://ftp.horde.org
d39 87
d145 7
a151 4
		  
	   3) Configure phplib. There are instructions for doing this in
 	      horde/phplib/README.
	      
d153 26
a178 26
	      
	      The first file is "horde.php3.dist", and it needs the most work.
	      Start by copying it to "horde.php3", then open it in an editor.
	      
	      Edit $default->horde_root_url, and set it to the part of the URL
	      where Horde is installed, without the server name. For instance,
	      If you want Horde at http://www.mikehardy.net/horde, you will
	      say '/horde' here.
	      
	      If you would like to turn on our automated problem reporting
	      page (users will be able to give you feedback), you should
	      change $default->problem_reporting to "true;" and enter the
	      email address to send reports to.
	      
	      Just as the problem reporting may be turned on, if you want
	      to have automatic account signups you should change the value
	      to "true;" and enter the correct email address, or implement
	      a signup script in the skeleton we provide with
	      <horde>/signup.php3
	      
	      
	      5) You now need to configure any horde applications you have
  	      installed. Please see their respective INSTALL files for more
	      details.
	      
	      
a269 1

d273 1
@


1.1.2.7
log
@As of Apache 1.3.6, access.conf and srm.conf are deprecated; reflect
this change of philosophy in the install docs.
@
text
@d126 2
a127 2
Adding something like the above to Apache's httpd.conf (Apache now
recommends that access.conf and srm.conf be left empty) will allow
@


1.1.2.8
log
@Raise the minimum required PHP version to 3.0.16, and add some verbage on
known bugs.
@
text
@d18 1
a18 1
 * PHP 3.0.16 or greater -- SEE NEXT SECTION
a23 30


------------
Notes on PHP
============

Versions of PHP earlier than 3.0.16 have bugs known to affect Horde.
Please save yourself (and the Horde mailing lists) hassles from these
known issues, and use PHP 3.0.16 or later.  (PHP 4 also works now.)

PHP needs to be compiled with IMAP support, and (depending on your
needs) probably with LDAP and MySQL/PostgreSQL support as well.

For RedHat users, PHP RPMs are available at ftp://ftp.horde.org/pub/RPMS/
which are patched to resolve problems known to affect Horde.

NOTE:  PHP 3.0.16 has a bug which can cause the following error:

    Warning: Bad message number

This is a PHP bug, not a Horde bug.  You need to patch PHP's imap.c to
fix the php3_imap_fetchheader() function (this is done in the RPM).

NOTE:  PHP 3.0.15 has a bug which will cause the following error:

    Warning: Wrong parameter count for imap_delete()

This is a PHP bug, not a Horde bug.  Use 3.0.16 or apply a patch.
PLEASE don't report this to the Horde mailing lists, where it's been
discussed many times already.
@


1.1.2.9
log
@Capitalization fixes (s/HORDE/Horde/ etc.)
@
text
@d1 1
a1 1
Horde Installation Guide
d14 1
a14 1
Requirements for Horde
d19 1
a19 1
 * a web server, preferably an SSL web server so that Horde modules can use a 
d22 1
a22 1
 * Database supported by phplib (MySQL or PostgreSQL definitely work)
d60 1
a60 1
          There are several ways to install and configure Horde.  The first
d62 1
a62 1
       for Horde available. You can find them either from ftp://ftp.horde.org
d66 1
a66 1
       get Horde installed and functioning on your system.
d144 1
a144 1
# Added for Horde   
d212 1
a212 1
Getting Help with Horde
d219 1
a219 1
There is a web page for Horde at http://web.horde.org/. There are also
d232 1
a232 1
about the status of Horde development is welcome to join it by sending
d243 1
a243 1
we have setup for the Horde projects.  You can find it at:
d257 1
a257 1
We hope you find Horde useful and easy to use.  We thank you for taking
@


1.1.2.10
log
@one more horde -> hordemgr fix, and adding urls for patches to the install
docs.
@
text
@a152 1
php3_track_vars On
d176 1
a176 1
The next 4 lines are what we need for things to work:
a180 2
php3_track_vars On

a202 1
php3_track_vars On
@


1.1.2.11
log
@Clearer pointers to PHP 3.0.16 imap.c patch.
@
text
@d45 1
a45 5
fix the php3_imap_fetchheader() function.  The patch is available here:

  http://cvsweb.php.net/cvsweb.cgi/functions/imap.c.diff?r1=1.87&r2=1.88&cvsroot=php3

This patch is included in the PHP SRPM at ftp://ftp.horde.org/pub/SRPMS/
@


1.1.2.12
log
@Added URL for the 3.0.15 patch.
@
text
@d57 1
a57 2
discussed many times already. The patch is available here:
  http://cvsweb.php.net/cvsweb.cgi/functions/imap.c.diff?r1=text&tr1=1.83&r2=text&tr2=1.85&f=u&cvsroot=php3
@


1.1.2.13
log
@Make sample code consistent with phplib/README:  current working directory
should be added to the phplib include_path.
@
text
@d155 1
a155 1
php3_include_path '.:/usr/lib/phplib'
@


1.1.2.14
log
@Clearer pointers to RedHat RPMs, and the accompanying README as the
definitive source of install instructions and list of prerequisites.
@
text
@d38 1
a38 3
which are patched to resolve problems known to affect Horde.  Please see
the README file accompanying the RPMs for installation instructions and
a complete list of all required RPMs.
d66 3
a68 5
       way is via a package; both Debian and RedHat packages are available
       for Horde. Debian packages can be found at http://horde.tdyc.com.
       RedHat packages can be found at ftp://ftp.horde.org/pub/RPMS/;
       please see the README file accompanying the RPMs for installation
       instructions and a complete list of all required RPMs.
@


1.1.2.15
log
@New URL for PHP patches.
@
text
@d49 1
a49 1
  http://cvsweb.php.net/viewcvs.cgi/php3/functions/imap.c.diff?r1=1.87&r2=1.88&diff_format=u
d60 1
a60 2

  http://cvsweb.php.net/viewcvs.cgi/php3/functions/imap.c.diff?r1=1.83&r2=1.85&diff_format=u
@


1.1.2.16
log
@Substantial edits/improvements to the docs:

(1)  horde/docs/INSTALL: correct subdirectory list
     ** I removed "horde/db" -- if you know something I don't, put it back.
(2)  Gut horde/scripts/database/MYSQL and point them to horde/docs/DATABASE
     ** The db-specific READMEs (esp. PostgreSQL) should get merged into
        horde/docs/DATABASE as we have time.
(3)  horde/docs/DATABASE: tell the user to reload, but not restart
(4)  */docs/INSTALL: clean up the extraction/directory rename instructions
(5)  horde/docs/DATABASE: mention dbpasswd.sh
(6)  */docs/INSTALL: strongly urge the user to use test.php3
(7)  other nits...

Most of these submitted by: Robin Whittle <rw@@firstpr.com.au>
@
text
@a5 1
Copyright 2000 Brent J. Nordquist <bjn@@horde.org>
d10 1
a10 3
$Author$
$Revision$
$Date$
d21 1
a21 1
 * phplib, included with the Horde distribution
d81 3
a83 2
           2)  untar/gzip it into the directory you want under your web
               tree; rename the directory from "horde-1.2.xx" to "horde"
d85 1
a85 1
               You should now have a directory structure like this:
d87 5
a91 1
                  horde
d93 2
a94 3
                  horde/docs
                  horde/graphics
                  horde/lib
a95 1
                  horde/phplib
d97 1
a97 2
                  horde/scripts/database   [where sql scripts are]
                  horde/templates
a122 2
	      5) You should test the Horde installation now (see next
	      section.
d124 1
a124 1
	      6) You now need to configure any Horde applications you have
a128 24
------------------------------
Testing the Horde Installation
==============================

A comprehensive testing script, horde/test.php3, is included in the
Horde distribution.  This script makes sure that Horde, PHP, PHPLIB, the
database, etc. are all configured properly to support Horde applications.
PLEASE make use of this excellent testing tool before reporting problems
to the mailing lists!

You should test your Horde installation by pointing your browser to:

    http://(your-site)/horde/test.php3

The resulting page will show a red "No" after any element of PHP,
PHPLIB, etc. that is not properly configured.  You should also use the
"Click here to test PHPLIB" link, followed by clicking the "Reload"
link a few times, to make sure the counter is incremented.

If test.php3 identifies any problems, please re-read the installation
instructions to make sure you haven't missed anything, and consult the
FAQ at http://faq.horde.org/ for solutions to common problems.


@


1.1.2.17
log
@Use example.com for example URLs, per RFC 2606.
@
text
@d11 3
a13 3
$Author: bjn $
$Revision: 1.1.2.16 $
$Date: 2000/06/27 14:59:47 $
d144 1
a144 1
    http://example.com/horde/test.php3
@


1.1.2.18
log
@Updating my email address (something I probably should have done
yesterday...)
@
text
@d5 1
a5 1
Copyright 1999 Jon Parise <jon@@horde.org>
d12 2
a13 2
$Revision: 1.1.2.17 $
$Date: 2000/07/31 13:13:05 $
@


1.1.2.19
log
@Add note about using the "optimized" php[3].ini, which seems to cause
problems.
@
text
@d5 1
a5 1
Copyright 1999, 2000 Jon Parise <jon@@horde.org>
d11 3
a13 3
$Author: jon $
$Revision: 1.1.2.18 $
$Date: 2000/08/22 15:20:50 $
a65 4
Also note that a number of users have reported problems when using the
"optimized" versions of the php[3].ini file that is distributed with PHP.
We recommend using the standard -dist version as a template for your local
php[3].ini.
@


1.1.2.20
log
@Actually the php[3].ini threw me at first, too, so to prevent confusion...
@
text
@d12 2
a13 2
$Revision: 1.1.2.19 $
$Date: 2000/08/22 15:34:37 $
d67 3
a69 3
"optimized" versions of the php.ini/php3.ini file that are distributed with
PHP.  We recommend using the standard -dist version as a template for your
local php.ini/php3.ini.
@


1.1.2.21
log
@Updated Red Hat packaging documentation for 1.2.0.  I was recently corrected
by a Red Hat employee, that "Red Hat" properly has a space between the two
words.  Sure enough, I notice that the only place where it's "RedHat" is
when it's a pathname.  Never noticed it.
@
text
@d11 3
a13 3
$Author: bjn $
$Revision: 1.1.2.20 $
$Date: 2000/08/22 16:49:15 $
d40 1
a40 1
For Red Hat users, PHP RPMs are available at ftp://ftp.horde.org/pub/RPMS/
d76 1
a76 1
       way is via a package; both Debian and Red Hat packages are available
d78 1
a78 1
       Red Hat packages can be found at ftp://ftp.horde.org/pub/RPMS/;
@


1.1.2.22
log
@IfModule logic to support both PHP3 and PHP4 in httpd.conf files.

Submitted by: Matt Biermann <biermanm@@kirtland.cc.mi.us>
Submitted by: GOMEZ Henri <hgomez@@slib.fr>
Submitted by: Dan Brown <danb35@@earthlink.net>
@
text
@d12 2
a13 2
$Revision: 1.1.2.21 $
$Date: 2000/08/23 01:54:48 $
d172 2
a173 2
DocumentRoot /home/httpd/html/horde/
Alias /horde/ /home/httpd/html/horde/
d176 1
a176 1
Where "/home/httpd/html/horde/" is where ever you have installed the
d186 9
a194 17
<Directory /home/httpd/html/horde>  
    Options Indexes FollowSymLinks
    AllowOverride None
    order allow,deny
    allow from all
    <IfModule mod_php3.c>
        php3_include_path '/home/httpd/phplib:.'
        php3_auto_prepend_file /home/httpd/phplib/prepend.php3
        php3_magic_quotes_gpc Off
        php3_track_vars On
    </IfModule>
    <IfModule mod_php4.c>
        php_value include_path '/home/httpd/phplib:.'
        php_value auto_prepend_file /home/httpd/phplib/prepend.php3
        php_flag magic_quotes_gpc Off
        php_flag track_vars On
    </IfModule>
a196 3
(Of course, you need to change "/home/httpd/html/horde" to the path
where you have Horde installed on your system, and "/home/httpd/phplib"
to the path where you have PHPLIB installed.)
d210 4
a213 4
    Options Indexes FollowSymLinks
    AllowOverride None
    order allow,deny
    allow from all
d218 6
a223 1
The next lines are what we need for things to work:
a224 12
    <IfModule mod_php3.c>
        php3_include_path '/home/httpd/phplib:.'
        php3_auto_prepend_file /home/httpd/phplib/prepend.php3
        php3_magic_quotes_gpc Off
        php3_track_vars On
    </IfModule>
    <IfModule mod_php4.c>
        php_value include_path '/home/httpd/phplib:.'
        php_value auto_prepend_file /home/httpd/phplib/prepend.php3
        php_flag magic_quotes_gpc Off
        php_flag track_vars On
    </IfModule>
d230 21
d253 1
a253 3
file.  Also please read imp/docs/SECURITY for security recommendations,
and additional httpd.conf lines you can add to protect sensitive data (e.g.
passwords) in your Horde/IMP configuration files.
@


1.1.2.23
log
@s/horde.org/lists.horde.org/ for mailing lists.
@
text
@d12 2
a13 2
$Revision: 1.1.2.22 $
$Date: 2000/09/19 14:53:09 $
d265 2
a266 2
bug questions, discussion, etc. It is imp@@lists.horde.org, and you can
subscribe by sending an emp ty email to imp-subscribe@@lists.horde.org.
d268 1
a268 1
The second list is the developers list at dev@@lists.horde.org, and it is
d271 1
a271 1
sending an empty mail to dev-subscribe@@lists.horde.org.
d273 2
a274 2
The third list is the CVS list at cvs@@lists.horde.org, and most of the mail
on it is automatically generated announcements of changes to the CVS code.
d277 1
a277 1
email to cvs-subscribe@@lists.horde.org.
d307 1
a307 1
dev@@lists.horde.org
@


1.1.2.24
log
@Pointers to 3.0.17 patches to fix upload bug.
@
text
@d12 2
a13 2
$Revision: 1.1.2.23 $
$Date: 2000/10/18 19:52:46 $
a44 10
NOTE:  PHP 3.0.17 has a bug which causes Apache to crash on file uploads.
The symptom is usually a "Document contains no data" message when the
Apache process on the server segmentation faults.

This is a PHP bug, not a Horde bug.  You need to patch PHP to fix this;
the patches are available here:

    http://marc.theaimsgroup.com/?l=php-dev&m=97171796329239&q=p3
    http://marc.theaimsgroup.com/?l=php-dev&m=97174635324591&q=p3

d52 1
a52 1
    http://cvsweb.php.net/viewcvs.cgi/php3/functions/imap.c.diff?r1=1.87&r2=1.88&diff_format=u
d55 10
@


1.1.2.25
log
@...and add register_globals to Apache config. and documentation.
@
text
@d12 2
a13 2
$Revision: 1.1.2.24 $
$Date: 2000/10/26 18:52:59 $
a199 1
        php_flag register_globals On
a239 1
        php_flag register_globals On
@


