[horde] cvs ... and then-- why do we have to create all these symlinks, and it's still screwy?

w trillich will at serensoft.com
Sun Jun 5 09:14:04 PDT 2005


hi. first-time poster to this list. having trouble understanding 
how to interrelate the modules to get them to work under apache 
(apache2)... are we missing some links? do we need to move the 
module directories around somewhere?



horde looks like it'll be delightful for what we're doing (small 
real estate company with a hundred field agents or so, email, 
subdomains) once we get it set up.

aye, there's the rub.

we're spoiled by the debian "apt-get install" but alas, few 
horde packages are debianized, and they're not just old, they're 
ancient.

so we did the cvs dance:

    export CVSROOT=:pserver:cvsread at anoncvs.horde.org:/repository
    cvs co -r FRAMEWORK_e \
       horde framework imp ingo nag mnemo kronolith

and we've got lots of stuff now:

drwxr-xr-x  64 root root   4096 2005-06-05 10:47 framework/
drwxr-xr-x  15 root root   4096 2005-06-05 10:47 horde/
drwxr-xr-x  13 root root   4096 2005-06-05 10:47 imp/
drwxr-xr-x  11 root root   4096 2005-06-05 10:47 ingo/
drwxr-xr-x  12 root root   4096 2005-06-05 10:47 kronolith/
drwxr-xr-x  12 root root   4096 2005-06-05 10:47 mnemo/
drwxr-xr-x  12 root root   4096 2005-06-05 10:47 nag/

note that horde is by itself; imp is by itself; nag is by 
itself; and on and on. each has its own directory, and that 
comes into play shortly.

(once we ran across the instrux for it, we also did the "php4 
framework/install-packages.php" which threw no error messages, 
so that went well. creating the mysql tables was also a breeze.)

and...

we point our browser to the top of that directory tree (shown 
above, properly aliased under apache) and we get a listing of 
those elements. no surprise.

fine. we drill into /horde/ instead, and we see "The requested 
URL /horde/ was not found on this server." very funny.

so we "cd horde; ln -s . horde" and try again:

aha -- much better! even tho /horde *is* at the top of the 
directory chain, we had to have an entry point to itself within 
that directory. odd -- couldn't find that in the documentation 
anywhere.

but now, there's no "imp" and no "kronolith" and no anything 
else listed in the web interface, for that matter.

more links! "ln -s ../* ." and we try again (clicking 'log out' 
to reset the interface): success! we now have navigable items 
for mail/filters/organizing/calendar/notes/tasks. cool!

drwxr-xr-x   6 root      4096 2005-06-05 10:47 admin/
drwxr-xr-x   3 www-data  4096 2005-06-05 10:47 config/
-rw-r--r--   1 root     25275 2000-02-11 20:47 COPYING
drwxr-xr-x   2 root      4096 2005-06-05 10:47 CVS/
drwxr-xr-x   3 root      4096 2005-06-05 11:08 docs/
lrwxrwxrwx   1 root        12 2005-06-05 10:56 framework -> 
../framework/
lrwxrwxrwx   1 root         1 2005-06-05 10:54 horde -> ./
lrwxrwxrwx   1 root         6 2005-06-05 10:56 imp -> ../imp/
-rw-r--r--   1 root      2229 2005-03-02 01:10 index.php
lrwxrwxrwx   1 root         7 2005-06-05 10:56 ingo -> ../ingo/
drwxr-xr-x   3 root      4096 2005-05-25 15:17 js/
lrwxrwxrwx   1 root        12 2005-06-05 10:56 kronolith -> 
../kronolith/
drwxr-xr-x   4 root      4096 2005-06-05 10:47 lib/
drwxr-xr-x  40 root      4096 2005-06-05 10:47 locale/
-rw-r--r--   1 root      5842 2005-01-31 10:44 login.php
lrwxrwxrwx   1 root         8 2005-06-05 10:56 mnemo -> ../mnemo/
lrwxrwxrwx   1 root         6 2005-06-05 10:56 nag -> ../nag/
drwxr-xr-x   3 root      4096 2005-06-04 18:42 po/
-rw-r--r--   1 root      3032 2004-09-24 15:55 README
-rw-r--r--   1 root      2359 2005-01-03 06:25 rpc.php
drwxr-xr-x   6 root      4096 2005-06-05 10:47 scripts/
drwxr-xr-x  10 root      4096 2005-06-05 10:47 services/
-rw-r--r--   1 root      2501 2005-06-04 18:42 signup.php
drwxr-xr-x  19 root      4096 2005-06-05 10:47 templates/
-rw-r--r--   1 root     13692 2005-06-04 18:42 test.php
drwxr-xr-x  27 root      4096 2005-06-05 10:47 themes/
drwxr-xr-x   3 root      4096 2005-06-05 10:47 util/

better: no we see links for mail, filters, calendar, notes, 
tasks. yet -- clicking the 'mail' link gives us

    Warning: main(/root/horde/imp/lib/../../lib/core.php):
    failed to open stream: No such file or directory in
    /root/horde/imp/lib/base.php on line 27

    Fatal error: main(): Failed opening required
    '/root/horde/imp/lib/../../lib/core.php'
    (include_path='.:/usr/share/php') in
    /root/horde/imp/lib/base.php on line 27

similar brokenness on filters, calendar, notes, and tasks.

the ../../lib/core.php appears to be looking for the module 
horde/lib/core.php altho the directory structure as it is does 
NOT have imp or any other such module directory to be INSIDE the 
horde directory. yet that's what the above link is appearing to 
expect. did we do something evil?

===

so where's the documentation, surely it's out there, that shows 
how to take this cvs checkout and turn it into a workable horde? 
  the most promising text we've run across is the 
three-paragraph section between 'installing from cvs or 
snapshots' and 'configuring horde' inside horde/docs/INSTALL. 
without that we wouldn't have known about checking out framework 
and running "install-packages.php".

we've obviously missed something somewhere. please point. :)

===

Horde Version
Horde: 3.0.5-cvs

Horde Applications
Horde: 3.0.5-cvs
Imp: H3 (4.0.4-cvs) (run Imp tests)
Ingo: 1.0.2-cvs (run Ingo tests)
Kronolith: H3 (2.0.4-cvs)
Mnemo: 2.0.2-cvs
Nag: 2.0.2-cvs

PHP Version
View phpinfo() screen
View loaded extensions
PHP Version: 4.3.10-15
PHP Major Version: 4.3
PHP Minor Version: 10
PHP Subminor Version: 15
PHP Version Classification: release
You are running a supported version of PHP.

PHP Module Capabilities
Ctype Support: Yes
DOM XML Support: Yes
FTP Support: Yes
GD Support: Yes
Gettext Support: Yes
Iconv Support: Yes
IMAP Support: Yes
LDAP Support: Yes
Mbstring Support: Yes
Mcrypt Support: Yes
MIME Magic Support (fileinfo): No
The fileinfo PECL module or the mime_magic PHP extension (see 
below) will most likely provide faster MIME Magic lookups than 
the built-in Horde PHP magic code. See horde/docs/INSTALL for 
information on how to install PECL/PHP extensions.
MIME Magic Support (mime_magic): Yes
MySQL Support: Yes
OpenSSL Support: Yes
PostgreSQL Support: Yes
Session Support: Yes
XML Support: Yes
Zlib Support: Yes

Miscellaneous PHP Settings
magic_quotes_runtime disabled: Yes
memory_limit disabled: No
If PHP's internal memory limit is turned on and if not set high 
enough Horde will not be able to handle large data items (e.g. 
large mail attachments in IMP). If possible, you should disable 
the PHP memory limit by recompiling PHP without the 
"--enable-memory-limit" flag. If this is not possible, then you 
should set the value of memory_limit in php.ini to a 
sufficiently high value (Current value of memory_limit: 8M).
safe_mode disabled: Yes
session.use_trans_sid disabled: Yes
session.auto_start disabled: Yes

File Uploads
file_uploads enabled: Yes
upload_max_filesize: 2M
post_max_size: 8M

Required Horde Configuration Files
config/conf.php: Yes
config/mime_drivers.php: Yes
config/nls.php: Yes
config/prefs.php: Yes
config/registry.php: Yes

PHP Sessions
Session counter: 1
To unregister the session: click here

PEAR
PEAR Search Path (PHP's include_path):  .:/usr/share/php
PEAR: Yes
Recent PEAR: Yes
Mail: Yes
Mail_Mime: Yes
Log: Yes
DB: Yes
Net_Socket: Yes
Date: Yes
Auth_SASL: Yes
HTTP_Request: Yes
File: Yes
Net_SMTP: Yes
Services_Weather: Yes




More information about the horde mailing list