Kolab / Horde Workshop Report
 


The Kolab / Horde Workshop took place this past Saturday, and we all had a great time. We had 10 people come out, most with computers to setup on. We have a few pictures you can see in the Kolab / Horde Workshop gallery. As you can see, we had a couple new faces there, some past members, as well as some current members.

As with any workshop (so it seems), Mr. Murphy (as in Murphy's Law), made himself known via some technical issues. Luckily we were able to work around these and continue on. The tough part was to get Horde running on the same box Kolab was running on, but use the official release files. It turns out that the PHP support Kolab installs does not have support for a database. And unfortunately full integration between Kolab and Horde is not quite there yet. We found a solution, and then revised the solution some. You can learn about the first approach in the handout file. The revision is very simple really - don't do the IP aliasing suggested in the handout, and then tell Kolab's Apache not to listen to port 80. This means a simple removal of the "Listen 80" line from the corresponding config file (/kolab/etc/apache/apache.conf). Then installing Apache, mod_php, and PEAR outside of Horde - but don't let this server handle port 443 - Kolab's will take care of that. Of course, this is but one method, and with some extra digging (such as installing Kolab from source), one potentially could make horde work using Kolab's web server.

It appears most of the attendees left armed with the knowledge to tackle Kolab and Horde themselves, and I've had feedback from one of them that they have had success with only a couple minor issues.

If you are interested in installing Kolab yourself, download all the files in the most recent binary files (you don't need the source files) from ftp://ftp.belnet.be/packages/kolab/server/release/ and then follow the instructions in the 1st.README file. As for Horde, we put together a handout you can download.

I'd like to say thanks to Gustin for his assistance in the preparation for the workshop, and showing off the extent of what Horde could do. I'd also like to thank everyone who was able to make it.

Finally, for those who were there, recall the cyclic link error we were getting at the end of the day... I was able to work around this by switching the authentication to use IMP's, and temporarily renaming the INGO module directory (to ingo_old) until after I had logged in once. Everything is working like a charm now. Though I've since reinstalled my mail server and then put Horde on a different box.