head	2.8;
access;
symbols
	STABLE_1_0:1.10.2.2
	HORDE_1_2_0_pre3:2.5.2.4
	HORDE_1_2_0_pre2:2.5.2.2
	HORDE_1_2_0_pre1:2.5.2.1
	STABLE_1_2__1_2_0_pre1:2.5.2.1
	horde__1_2_0_pre1:2.5.2.1
	STABLE_1_2:2.5.0.2
	STABLE_1_0_10:1.10.2.2
	STABLE_1_0_9:1.10.2.2
	STABLE_1_0_8:1.10.2.2
	STABLE_1_0_7:1.10.2.2
	STABLE_1_0_6:1.10.2.2
	CURRENT:2.1
	STABLE:1.10.0.2
	STABLE-2_0:1.10.0.4;
locks; strict;
comment	@# @;


2.8
date	99.08.26.13.09.24;	author rkrusty;	state dead;
branches;
next	2.7;

2.7
date	99.08.10.17.21.34;	author jon;	state Exp;
branches;
next	2.6;

2.6
date	99.08.05.03.57.59;	author mhardy;	state Exp;
branches;
next	2.5;

2.5
date	99.08.05.01.21.51;	author mhardy;	state Exp;
branches
	2.5.2.1;
next	2.4;

2.4
date	99.08.05.00.12.04;	author mhardy;	state Exp;
branches;
next	2.3;

2.3
date	99.08.04.23.04.46;	author mhardy;	state Exp;
branches;
next	2.2;

2.2
date	99.08.04.07.03.21;	author mhardy;	state Exp;
branches;
next	2.1;

2.1
date	99.05.05.01.40.25;	author mhardy;	state Exp;
branches;
next	2.0;

2.0
date	99.04.28.11.41.13;	author mhardy;	state Exp;
branches;
next	1.10;

1.10
date	99.04.21.23.18.50;	author rkrusty;	state Exp;
branches
	1.10.2.1;
next	1.9;

1.9
date	99.04.20.08.51.31;	author rkrusty;	state Exp;
branches;
next	1.8;

1.8
date	99.04.15.23.02.56;	author rkrusty;	state Exp;
branches;
next	1.7;

1.7
date	99.04.14.23.44.00;	author mhardy;	state Exp;
branches;
next	1.6;

1.6
date	99.04.14.18.39.11;	author rkrusty;	state Exp;
branches;
next	1.5;

1.5
date	99.04.04.12.50.56;	author rkrusty;	state Exp;
branches;
next	1.4;

1.4
date	99.04.04.04.35.15;	author mhardy;	state Exp;
branches;
next	1.3;

1.3
date	99.04.02.22.16.36;	author rkrusty;	state Exp;
branches;
next	1.2;

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

1.1
date	99.03.29.03.41.01;	author rkrusty;	state Exp;
branches;
next	;

1.10.2.1
date	99.04.29.03.51.51;	author rkrusty;	state Exp;
branches;
next	1.10.2.2;

1.10.2.2
date	99.05.05.01.41.12;	author mhardy;	state Exp;
branches;
next	;

2.5.2.1
date	99.08.05.03.57.37;	author mhardy;	state Exp;
branches;
next	2.5.2.2;

2.5.2.2
date	99.08.09.05.07.05;	author mhardy;	state Exp;
branches;
next	2.5.2.3;

2.5.2.3
date	99.08.10.03.59.37;	author mhardy;	state Exp;
branches;
next	2.5.2.4;

2.5.2.4
date	99.08.10.17.17.53;	author jon;	state Exp;
branches;
next	2.5.2.5;

2.5.2.5
date	99.08.22.10.38.45;	author rkrusty;	state Exp;
branches;
next	2.5.2.6;

2.5.2.6
date	99.08.23.23.30.59;	author rkrusty;	state Exp;
branches;
next	2.5.2.7;

2.5.2.7
date	99.08.24.15.27.23;	author rkrusty;	state Exp;
branches;
next	2.5.2.8;

2.5.2.8
date	99.08.25.03.32.44;	author rkrusty;	state Exp;
branches;
next	2.5.2.9;

2.5.2.9
date	99.08.25.03.35.54;	author rkrusty;	state Exp;
branches;
next	2.5.2.10;

2.5.2.10
date	99.08.25.04.00.17;	author rkrusty;	state Exp;
branches;
next	2.5.2.11;

2.5.2.11
date	99.08.25.04.48.54;	author rkrusty;	state dead;
branches;
next	;


desc
@@


2.8
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
@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/10/1999 


---------------------- 
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
 * MySQL installed and configured so your webserver can access it (or a 
	willingness to try shared memory in PHPLib)


-----------------------
Methods of 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).

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


	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


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

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


	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)

-=-=-=-=
Manually
-=-=-=-=

          Here is the process for doing all of this by hand.

           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/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://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.

		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.



-----------------------
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
horde@@horde.org
----------------------------------------------------------------------
@


2.7
log
@
jon: committed my the changes to the devel tree
@
text
@@


2.6
log
@Mike: putting the documentation updates on the tip revision as well
@
text
@d5 1
d10 1
a10 1
Last Updated: 08/03/99 
d22 2
a23 1
 * MySQL Installed and configured so your webserver can access it
d31 4
a34 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).
d66 9
a74 1

d95 5
a99 5
	1) Use MySQL, don't attempt to use anything else yet
	2) let me just re-iterate that you should use MySQL right now.
	3) See #1
	4) You'll need to create a "horde" database
	5) You'll need to execute the file create_database.mysql from
d101 1
a101 1

d133 20
a152 1
           4) In horde/config you will find a few files.  
a153 1
                [...FIXME insert config info here...]
d234 2
a235 2
about the status of IMP development is welcome to join it by sending email
to imp-cvs-subscribe@@horde.org.
@


2.5
log
@Mike:

o If you have an active session, leave IMP, and come back, the menu and
folders understand that you had a session and display themselves (this
matches what the status and mailbox frames were doing)

o I'm still not getting preferences to work despite having the DB
tables now, I assume that will change when Chuck rips out the
newer,better stuff. This may be my bad though

o The INSTALL file now gets you almost completely running with PHPLib,
MySQL, Horde, and IMP

o I get the contents of horde_loginform.ihtml in the folder and menu
frames when I click logout. That's deep PHPLib stuff referenced in
local.inc that I don't know about, and it goes away when I refresh the
frames, FWIW. ??

I'll branch Horde and IMP now, I guess. There's much work to be done to
make this truly friendly though. The sessions stuff rocks, its just not
friendly :-)
@
text
@d4 1
a23 9
-------------------
Supported Languages
===================

  English
  German

  ??? THERE ARE OTHERS (FIXME BEFORE RELEASE) ???

a90 15
	6) FIXME what SQL file do we run to get preference storage?


-=-=-=-=-=-=-=-
Web-based Setup
-=-=-=-=-=-=-=-

	1) Grab the latest version of Horde and IMP in tarball form
	2) Unpack Horde, change its name from Horde-1.2.x to "horde"
	3) Unpack IMP under the horde directory, change its name to "imp"
	4) In the horde directory, type 'sh ./install.sh'
	5) Point your browser to http://your.com/path/to/horde/setup.php3
	6) Answer all the questions, choose MySQL for your database
	7) In the horde directory, type 'sh ./secure.sh'

d101 2
a102 1
           2)  untar/gzip it into the directory you want.
d119 3
a121 1
                  ./build.pl --database=mysql
d125 1
a125 1
                [...insert config info here...]
d189 2
a190 2
There is an online, user-editable FAQ at http://horde.org/faq/. Use it, and
add anything that you run into to it, so that others can benefit from
d193 15
a207 14
There is a web page for HORDE at http://web.horde.org/. There are also two
mailing lists. One is the general IMP list, for development, discussion,
etc. It is imp@@horde.org, and you can subscribe by sending an empty email to
imp-subscribe@@horde.org.

The other list is the CVS commits list, 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 IMP development is welcome to join it by sending email to
imp-cvs-subscribe@@horde.org.

There are also web archives of both mailing lists. See, respectively:
  http://horde.tdyc.com

d209 2
d216 1
a216 1
    If you have found a bug you can add it to the Bug Tracking System
@


2.5.2.1
log
@Mike: more doc updates, this time in the Horde directory...
@
text
@a3 1
Copyright 1999 Mike Hardy <mikeh@@spark.com>
d23 9
d99 15
d124 1
a124 2
           2)  untar/gzip it into the directory you want. Move the
	       directory from "horde-1.2.xx" to "horde"
d141 1
a141 3
                  ./build.pl --help

			It will display usage instructions.
d145 1
a145 1
                [...FIXME insert config info here...]
d209 2
a210 2
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
d213 14
a226 15
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 IMP development is welcome to join it by sending email
to imp-cvs-subscribe@@horde.org.
a227 2
There are also web archives of all the mailing lists. See:
  http://horde.tdyc.com                                    
d233 1
a233 1
    If you have found a bug you can add it to the Bugzilla bug system
@


2.5.2.2
log
@Mike: I should probably make sure the documents are up to date with the
changes before I go through the trouble of making a new release, no? Well,
they're up to date now I think, with the shared memory information in
there as well as the LDAP for the local.inc changes (nice cleanup there,
btw)
@
text
@d9 1
a9 1
Last Updated: 08/08/1999 
d21 1
a21 2
 * MySQL Installed and configured so your webserver can access it (or a 
	willingness to try shared memory in PHPLib)
d64 1
a64 5
	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.
d85 6
a90 2
	If you're using a database (like MySQL in this example), you'll
	need to do these two things:
a91 4
	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)
@


2.5.2.3
log
@Mike: documentation updates, and a setup.php3 fix (a fatal one, d'oh!)

Still getting this error from menu.php3 (everything else is fine):

Fatal error: HordeDefaultAuth is not a class in page.inc on line 26

I haven't had a chance to look at it yet, but I'm out of time right now...
@
text
@a70 3
		NOTE: for shared memory to work, it must be built into PHP.
			At least in RedHat's packages, this is not the case.

d128 1
a128 20
           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
d130 1
@


2.5.2.4
log
@
jon: a few changes / cleanups
@
text
@a4 1
Copyright 1999 Jon Parise <parise@@pobox.com>
d21 1
a21 1
 * MySQL installed and configured so your webserver can access it (or a 
d30 4
a33 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).
a72 1
            Shared memory is only available on Linux and Solaris.
d232 2
a233 2
about the status of HORDE development is welcome to join it by sending
email to cvs-subscribe@@horde.org.
@


2.5.2.5
log
@[IEM] New finish translations thanks to leo.jaaskelainen@@kolumbus.fi
(and yes, I'll add them to the head branch
@
text
@a209 1
====== Using Apache's config files to handle phplib prepends ========
a210 64
# Added for HORDE   
<Directory /usr/share/horde>  
Options Indexes FollowSymLinks
AllowOverride None
order allow,deny
allow from all
php3_include_path /usr/lib/phplib:/etc/horde
php3_auto_prepend_file /etc/horde/prepend.php3
</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 2 lines are what we need for things to work:

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

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/phplib:/home/httpd/html/horde
php3_auto_prepend_file /home/httpd/phplib/prepend.php3
</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.  
@


2.5.2.6
log
@[IEM] updating docs to include php3_magic_quotes_gpc Off
@
text
@d243 1
a243 1
The next 3 lines are what we need for things to work:
a246 1
php3_magic_quotes_gpc Off
a269 1
php3_magic_quotes_gpc Off
@


2.5.2.7
log
@[IEM] Updating CHANGES and INSTALL (along with tons of debian stuff)

   Updated: documtation about database changes/creation
   Notes on magic_quotes and per directory phplib config
@
text
@a79 2
        These commands can also be added on a per directory bases.  See
        the Apache section further down for more information.
d83 2
a84 2
	3) Disable magic_quotes_gpc (change them to "Off") in your php.ini
        
a102 5
        These create scripts can now be found in config/scripts ready to
        go for building your horde database.  They are designed to be
        the first thing run against your database.  (ie..it will try to
        create the horde database).  

d173 1
a173 1
           Moore II.  It is available from http://horde.tdyc.com/
d218 1
a218 1
php3_include_path /etc/horde:/usr/lib/phplib
a219 1
php3_magic_quotes_gpc Off
d245 1
a245 1
php3_include_path /etc/horde:/usr/lib/phplib
d269 1
a269 1
php3_include_path /home/httpd/html/horde:/home/httpd/phplib
@


2.5.2.8
log
@[IEM] Documentation sweep for horde

    1> Walked through HELP/INSTALL/README redoing installation instructions
       where needed.
    2> Migrated the IMP DATABASE file into the HORDE tree making changes
       where necessary.  (will remove database pieces out of INSTALL
       soon enough.
    3> updated more debian junk
@
text
@d10 1
a10 1
Last Updated: 08/25/1999 [IEM]
d22 2
a23 2
 * Database supported by phplib (MySql or Postgresql definatly work)
     (or a willingness to try shared memory in PHPLib)
a29 7
          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.
d31 4
d36 2
a42 4
             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.

d45 1
a45 1
	for getting Horde running though. If you want to go beyond
a81 1

d110 3
a112 3
-=-=-
Horde 
-=-=-
d114 1
a114 1
          Now for Horde itself.
a128 1
                  horde/config/scripts   [where sql scripts are]
d340 2
a341 2
dev@@horde.org
---------------------------------------------------------------------
@


2.5.2.9
log
@[IEM] removing database calls. redirecting output to DATABASE
@
text
@d103 12
a114 2
        Please see the DATABASE file for help with configuring your
        HORDE database.
@


2.5.2.10
log
@[IEM] Updating the PHPLib portion of the install doc
@
text
@a80 15
        *** 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.

@


2.5.2.11
log
@[IEM] migrating all core documentaiton (except readme and copying) into
the docs/ sub directory
@
text
@@


2.4
log
@Mike: okay, I think we're just about at the branch/-pre point for
MySQL, anyway.
@
text
@d61 3
a63 2
	3) Go to your webserver's DocumentRoot
	4) Create a "php" directory
d66 5
a70 3
	6) Move the contents of <horde>/phplib/horde_phplib.inc to the
		new "php" directory, and name it "local.inc". (NOTE: if you
		already have PHPLib applications, append the contents or
d72 1
@


2.3
log
@Mike: Got a little bit further, PHP is now able to execute things, but
the setup stuff is *very* irritated at the module stuff that we were
just kvetching about on the list.

I had to manually include "ct_dbm.inc" after deleting all the other
PHP container classes in horde_phplib.inc/local.inc to get to this
point. Its documented in the INSTALL.
@
text
@d8 1
a8 1
Last Updated: 04/03/99 
d16 1
a16 1
 * php 3.0.7 or greater 
d20 1
a68 5
	7) I use DBM files for session storage, so edit the local.inc
		file and remove all of the HordeCT*** class entries
		except the HordeCTDbm one
	8) Add the line 'require "ct_dbm.inc";' to the top of the file

d86 26
a115 5

              The most common method of installing HORDE is to grab the tarball,
          untar it somewhere and run through the code making all the changes 
          you need by hand.  

d137 1
a137 1
                  ./build.pl
a138 3
              If you install IMP as well, you can use the setup.php3 process
          that comes with it to configure the HORDE libraries as well.
       
a153 6
                Packages are by far the easiest way to install any program.  
           The reason I say this is because most of the work is done for you.
           By the use of scripts the maintainer of the package take care of
           most configuration issues and the program because (most of the time)
           pretty much plug and play.   

d155 1
a155 1
           (there are probably more but these are teh ones I know of).
d169 2
a170 2
		Currently there is no RPM package. If you are interested in
	   maintaining one, please get in touch with us.
a173 2

-----------------------
@


2.2
log
@Mike: Ouch - water's still too hot for me, I'm retreating to my bed for
safety :-)

I've documented what I have so far at least (which isn't a whole lot and
doesn't work so well, obviously)
@
text
@d68 5
@


2.1
log
@Mike: Fixing stupid error in INSTALL files where the Apache Alias directive
I gave as an example had double-quotes around it when it shouldn't.
@
text
@d19 1
a19 1
 * PERL if you want to use the config scripts.
d29 2
d41 42
a162 28
PHP3 and Apache Changes
=======================


Well, not necessarily Apache, but your Web Server in general.  This piece
will cover what changes to your PHP3 and Web Server configuration you
need to do for things to work 100% (or pretty close).  

==php3.ini==

In your php3.ini file there are a few things you need to do so that 
content appears the way it should and also so that you can use key
features such as IMAP.  :)

First off, under the Data Handling section:

===Start===

;;;;;;;;;;;;;;;;;
; Data Handling ;
;;;;;;;;;;;;;;;;;
magic_quotes_gpc         = Off  ; magic quotes for incoming GET/POST/Cookie data
magic_quotes_runtime     = Off  ; magic quotes for runtime-generated data
magic_quotes_sybase      = Off  ; Use Sybase-style magic quotes

===End===

Make sure all your magic_quotes options are turned OFF!
d164 3
a166 3
If you need magic_quotes_gpc for another PHP application, you could also let 
magic_quotes_gpc = On on your php.ini and set it off per directory bases.
Just add the following lines on your access.conf apache configuration files :
a167 3
    <Directory /path/to/your/imp/directory>
    php3_magic_quotes_gpc Off
    </Directory>"
d169 1
a169 43

and under the Dynamic Extensions section:

===Start===

;;;;;;;;;;;;;;;;;;;;;;
; Dynamic Extensions ;
;;;;;;;;;;;;;;;;;;;;;;
; if you wish to have an extension loaded automaticly, use the
; following syntax:  extension=modulename.extension
; for example, on windows,
; extension=msql.dll
; or under UNIX,
; extension=msql.so
; Note that it should be the name of the module only, no directory information
; needs to go here.  Specify the location of the extension with the extension_dir directive above.
extension=imap.so      ; Added for IMAP support
extension=mysql.so     ; Added for MySql support
extension=pgsql.so     ; Added for PostgreSql support
extension=ldap.so      ; Added for LDAP support

===End===

You'll need to add the appropriate extensions for what you'll be using.  
Remember that if your running this server on a Windows box you'll be using
.dll extensions instead of .so extensions.   

===Apache's srm.conf===

Now this file can look different depending on version and configuration so
I will just show the actual line within the file that we are concerned
with.

DirectoryIndex index.html index.php3 index.htm default.html index.cgi

You need to make sure that index.php3 is listed in your DirectoryIndex
line in order for Horde to show up properly. I'm sure this line is 
called different things with different servers but the basic idea is
that you want the index.php3 file to be a default in the same sense that
index.html is.  


===== Putting IMP as Apache's web-root ==========
d210 1
a210 2
  http://www.horde.org/mail/imp/
  http://www.horde.org/mail/cvs
a235 5
This version of the Installation manual was slapped together in part
by Ivan, Mike, Jason and of course, the man who started it all, the
man who keeps us on our toes, the man who'll probably never notice I
put this here but if he does I'm a dead man...Chuck.

d238 2
a239 2
Chuck Hagenbuch and the IMP team
chuck@@horde.org
@


2.0
log
@Mike: Bumping all revisions to 2.0
@
text
@d206 1
a206 1
Alias /horde/ "/home/httpd/htdocs/horde/"
@


1.10
log
@[IEM] Updating instructions
@
text
@@


1.10.2.1
log
@[IEM] Minor update

kewl..it says stable...woohoo...  (I'm too easily impressed)
@
text
@d8 1
a8 1
Last Updated: 04/29/99 
d104 1
a104 1
           Moore II.  It is available from http://master.debian.org/~rkrusty
@


1.10.2.2
log
@Mike: Fixing stupid mistake where the Apache Alias example I give has double-
quites when it shouldn't.
@
text
@d206 1
a206 1
Alias /horde/ /home/httpd/htdocs/horde/
@


1.9
log
@[IEM] adding German to the list of supported languages
@
text
@d28 1
d239 2
a240 2
  http://web.horde.org/mail/imp/
  http://web.horde.org/mail/cvs
d251 1
a251 1
http://web.horde.org/bugs
@


1.8
log
@[IEM] adding a supported languages piece
@
text
@d27 1
a27 1

@


1.7
log
@Mike: Documented how to make Horde or IMP the web-root of a server
@
text
@d22 5
@


1.6
log
@[IEM] beginning of documentation updates
@
text
@d111 101
@


1.5
log
@[IEM] updating documentation to reflect a suggestion of checking individual
modules INSTALL files.
@
text
@d57 5
d70 5
a74 1
           4) You now need to configure any modules you have installed. Please
d77 2
@


1.4
log
@Mike: updated the horde-specific one as well
@
text
@a63 1
          Please see the INSTALL file in the IMP distribution for more details.
d65 3
a67 1

@


1.3
log
@[IEM] Updated installation procedures to reflect new file layout
@
text
@d8 2
a9 1
Last Updated: 04/02/99 
d15 1
a16 4
 * a database (mysql/postgresql are mostly supported, there are some other
     database libs - see the lib/ directory) for the above mentioned
     addressbook or prefs saving, although using the prefs and addressbook is
     currently optional.
d21 2
d27 1
d33 1
a33 3
====================
1) Auto-Manipulation
--------------------
d39 1
d50 1
a50 2

           3) make sure your directory structure is like this:
d58 1
a58 3
           4) go into horde/lib/src and run the following command:

                  ./buildlib.pl
a59 2
                      or
 
a61 20
              The difference is this.  buildlib.pl wants you to pass
           some variables to it.  By running ./buildlib.pl by itself
           it will tell you want variables it's looking for.  

              build.pl doesn't require anything to be passed.  It just
           assumes you want the generic stuff.  The one nice thing about
           build.pl is that you can create a file called build.opts in that
           same directory and put all your options you want to use in that
           file in this format:

                          option=value

              An example of this would be:

                          database=postgres

              When build.pl runs it will check that file and use any values
          in it as defaults.  This is nice for keeping your configuration the
          same and automating upgrades/installs.

d67 5
a71 3
===========
2) Packages
-----------
d79 1
a79 1
                Currently there are 3 types packaging out there in use.
d82 2
a83 2
           .rpm extension, Debian Package format which  has a .deb
           extension, and the old fashion .tar.gz package.
d94 5
d103 1
d123 2
d137 1
a137 1
specific to a browser or operating system.  So please be thourogh.  In
d140 2
@


1.2
log
@[IEM] Finished the horde INSTALL manual (i think)
@
text
@d55 2
a56 1
                  horde/src
d59 1
a59 1
           4) go into horde/src and run the following command:
@


1.1
log
@[IEM] added based text files for "horde" module
@
text
@d2 2
a3 1
Copyright 1999 Charles J. Hagenbuch <chuck@@horde.org>
d8 2
d12 1
a12 1
----------------------
d14 7
a20 1
 * php 3.0.7 or greater
d23 36
a58 7
-------------
What is HORDE
-------------

HORDE is the core piece to a suite of web based applications.  It is
required for any of them to work.  Currently the only fully functional
"module" is IMP, a web based mail client.  
d60 46
a105 3
--------------------------
Methods of Installation
--------------------------
d107 8
a114 1
[...] Soon to come
d118 1
a118 1
-----------------------
d124 41
a164 1
---------------------------------------
d166 1
a166 1
Enjoy, Chuck Hagenbuch and the HORDE team
d168 1
@

