Kolab from individual components

[Gunnar Wrobel]

Quoting Alexander Schröter <webmaster at computational-chemistry.org>:

> Am 16.03.2010 22:33, schrieb Promani NV:
>> Hello,
>>
>> I'm researching the possibility to use Kolab to replace
>> an Exchange server (OK that's what everyone probably wants).
>> On the client side I've tried Bynari with a regular IMAP
>> server. I would also like to use Horde.
>>
>> However, I do have most of Kolab's components already running
>> on another server and spend a lot of time configuring. It would
>> be a shame to throw away all the tweaking work, so I'd like to
>> know what 'added value' Kolab provides over the individual
>> components and has anyone "cloned" Kolab on their own? Is
>> this a doable thing (eg are LDAP schemes available and how
>> would the free/busy be handled, etc).
>>
>> Regards,
>> Joris
>>
> Hi I know what you mean and I have been thinking a lot about this.
>
> I started out with a kolab installation with openpkg. But soon I ran
> into problems regarding the openpkg packages and their lack of easy
> installable/updateable packages that I want to use or try. So I did a
> lot of fiddeling around till I finaly came to the conclusion that this
> could not be the right way.
>
> So my next step was the debian native package, which I think (of course
> for your distribution) could be an option for you. I guess it would be
> your job to merge your existing configuration with the one from the
> package. But keep in mind that changing the configuration (even though
> you think of it as tweaking) has its drawbacks and you might break the
> system. Kolab is a real beast with lots of components which would also
> get updated and this would then depends on your distribution.
>
> I now reached a compromise where I am using the openpkg packages but
> have a couple of them replaced with native packages. So far *knock on
> wood* all works fine. And I have the advantage of the support through
> the kolab community because I basicly use openpkg and can update kolab
> like everybody else with each release but also the advantage of adding
> components from standard debian packages as long as I am willing to work
> on integrating them into the system.
>
> I advise trying it out on a testsystem, and I mean both native and
> openpkg. There are definitly parts which are easy to exchange but
> keeping them work together is the challenge.

Yup. And it is very easy to underestimate the effort it might take to  
keep the do-it-yourself system running. Groupware servers are rather  
complex and the fact that you have a team of developers test the  
system thoroughly before it is being deployed has a significant value.

Cheers,

Gunnar

> To answer your question I
> think it would be doable but in my opinion (of course everybody has to
> decide for himself) not recommendet.
>



> However, good luck.
> Alexander
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users
>



-- 
______ http://kdab.com _______________ http://kolab-konsortium.com _

p at rdus Kolab work is funded in part by KDAB and the Kolab Konsortium

____ http://www.pardus.de _________________ http://gunnarwrobel.de _
E-mail : p at rdus.de                                 Dr. Gunnar Wrobel
Tel.   : +49 700 6245 0000                          Bundesstrasse 29
Fax    : +49 721 1513 52322                          D-20146 Hamburg
--------------------------------------------------------------------
    >> Mail at ease - Rent a kolab groupware server at p at rdus <<
--------------------------------------------------------------------