blob: fa02fefea7bc120faee978b163de6060270a6d68 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
|
************************************************************************
Horde has been installed in %%HORDIR%% with your blank
configuration files.
WARNING! the first user will get logged in as an administrator!
********
If you want Horde to access a database, you have to run the
appropriate scripts located in %%HORDIR%%/scripts/sql.
It is recommended that you change the password of the 'hordemgr'
user used to connect to the horde database.
Horde is setup by default to access MySQL.
WARNING! if you are upgrading from Horde v. 3.0.x, you have to alter your
******** database schemas. Please read the doc UPGRADING.
You can now access Horde without a password at <http://localhost/horde/>,
and you will be logged in as an administrator. You should first configure
a real authentication backend. Click on "Setup" in the "Administration"
menu and configure Horde. Start in the "Authentication" tab.
See the doc in %%DOCSDIR%% for details.
(tip: if you plan to install IMP, just keep "Automatic authentication as
a certain user", add your login to be treated as administrator, and once
IMP will be installed, switch to "Let a Horde application handle auth").
Select a log driver; if you keep 'file', do not forget to add a line
in /etc/newsyslog.conf.
Then select and configure a preferences driver.
When everything is OK, you should be able to access Horde from
<http://localhost/horde/>.
There is a testing script at <http://localhost/horde/test.php>.
************************************************************************
|
