head	1.1;
access;
symbols
	HORDE_1_2_7:1.1.2.3
	HORDE_1_2_6:1.1.2.3
	HORDE_1_2_5:1.1.2.3
	HORDE_1_2_4:1.1.2.3
	HORDE_1_2_3:1.1.2.3
	HORDE_1_2_2:1.1.2.3
	HORDE_1_2_1:1.1.2.3
	HORDE_1_2_0:1.1.2.3
	HORDE_1_2_0_pre14:1.1.2.3
	HORDE_1_2_0_pre13:1.1.2.2
	STABLE_1_2:1.1.0.2;
locks; strict;
comment	@# @;


1.1
date	2000.04.09.20.34.56;	author chuck;	state dead;
branches
	1.1.2.1;
next	;

1.1.2.1
date	2000.04.09.20.34.56;	author chuck;	state Exp;
branches;
next	1.1.2.2;

1.1.2.2
date	2000.05.30.03.24.20;	author bjn;	state Exp;
branches;
next	1.1.2.3;

1.1.2.3
date	2000.06.27.14.59.49;	author bjn;	state Exp;
branches;
next	;


desc
@@


1.1
log
@file MYSQL was initially added on branch STABLE_1_2.
@
text
@@


1.1.2.1
log
@database README files and setup scripts for supported platforms. phplib
pieces coming soon for oracle, ifmx, and sybase
@
text
@a0 18
Due to the fact that I can't tell if you have made any changes to your mysql
server let alone what the password is for it you will have to configure the
mysql server by hand.

There is a file in this directory (horde/scripts/database/) that all you
have to do is run the command:

mysql < mysql_create.sql

and it will populate your database for you. That exact command line will
only work if you run it from root and mysql has no password set for the root
account. Please note that the database configuration in the mysql_create.sql
matches that which is configured within imp. This way if you install imp and
then setup your mysql database using the example above, it should work out
of the box. You will need to restart both your mysql server and apache after
this. If you make changes to the name of the database, the manager name or
password, you will need to make the same changes to your
imp/config/defaults.php3 file as well.
@


1.1.2.2
log
@Nits and typos.  mysql_create.sql needs to flush privileges after adding
the hordemgr user or we'll get bug reports.
@
text
@d18 1
a18 1
imp/config/defaults.php3 and phplib/local.inc files as well.
@


1.1.2.3
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
@d1 18
a18 2
Please consult the file horde/docs/DATABASE for instructions on configuring
MySQL for Horde.
@


