new domains without changes to /etc/kolab/kolab.conf OR "pure" LDAP-only administration

[Erik M Jacobs]

Hi Timotheus,

That is great news!

Does anyone know when these will make it to the development repo from
the nightlies?

Erik M Jacobs
Director, JumpShip Services
A Division of EjectButton, Ltd
PGP Key ID: 9CA64161

On 10/10/2013 05:49 AM, Timotheus Pokorra wrote:
> Hello Erik,
> I have now done a test with the latest Kolab 3.1 version from
> git.kolab.org (available as nightly build for CentOS, see [1]).
> I was able to add a new domain, and to create users in that domain,
> without changing the kolab.conf file.
> There was still one bug ([2]) that was resolved in the past days, that
> prevented that.
> 
> You still have to set some parameters in kolab.conf once, but I guess
> that is ok.
> see for suggestions
> https://github.com/tpokorra/kolab3_tbits_scripts/blob/master/kolab3.1/initMultiDomain.sh
> eg this line is important:
> https://github.com/tpokorra/kolab3_tbits_scripts/blob/master/kolab3.1/initMultiDomain.sh#L68
> to set the default for primary_mail, so that it will be used in all
> additional domains.
> 
> So if you are happy with the folders that are autocreated, there is no need for
> https://github.com/tpokorra/kolab3_tbits_scripts/blob/master/kolab3.1/addDomain.php
> and
> https://github.com/tpokorra/kolab3_tbits_scripts/blob/master/kolab3.1/domain.kolab.conf.tpl
> anymore.
> 
> All the best,
>   Timotheus
> 
> [1] http://kolab.org/blog/timotheus-pokorra/2013/09/27/install-nightly-build-git.kolab.org-master
> [2] https://issues.kolab.org/show_bug.cgi?id=2306
> 
>> Anyone know if there are any plans to move away from that?
>>