[Kolab-devel] [issue717] Make design goal of kolab_bootstrap easier to understand

[Bernhard Reiter]

New submission from Bernhard Reiter <bernhard at intevation.de>:

Kolab Server 2.0-beta4 (and CVS):

Administrators easily believe kolab_bootstrap is very important,
though it is just a hack to get a running installation to create
kolab.conf, the initial ldap contents, the certificates and all this.

The running system kolab.conf, the templates and ldap are the places
to actually configure the system and then run kolabconf.

We should put a few measures in place to prevent this confusion.
What about moving kolab.conf.template to a different place?
Maybe in a subdirectory bootstrap somewhere?

Second idea: Add a warning message to kolab_bootstrap?
What do you think?

----------
assignedto: steffen
messages: 4376
nosy: bernhard, bh, martin, steffen
priority: minor bug
status: unread
title: Make design goal of kolab_bootstrap easier to understand
topic: kkc, server
________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://intevation.de/roundup/kolab/issue717>
________________________________________________