[Kolab-devel] Kolab-CF and Template file handling

[Bo Thorsen]

On Thursday 22 January 2004 10:38, Stephan Buys wrote:
> Hi all,
>
> As per a request on the Kroupware mailing list (and due to our
> work with Horde/Kolab Web Client) we are about to introduce dynamic
> Template File handling into kolab-cf.
>
> I thought I would share our design decisions with you so that we can
> cater for everyone's needs:
>
> - All template files will be stored under KOLABDIR/etc/kolab/templates
> - Each template file will contain a META data section at the top of the
> file Example main.cf.template:
>
> START_KOLAB_META
> TEMPLATE_DEST = $prefix/etc/kolab/postfix/main.cf
> CHANGED_CMD = $prefix/etc/rc postfix reload
> END_KOLAB_META
> ....rest of main.cf.template follows as usual
>
> TEMPLATE_DEST will contain the destination of the template file
> CHANGED_CMD will contain the command to be executed if something has
> been changed in the configuration file.
>
> - When writing the template file to TEMPLATE_DEST the all the lines up
> until END_KOLAB_META will be stripped from the file.
>
> Does this sound like a good mechanism to all?
> This will allow anyone to start managing their services from the kolab
> daemon by just placing a template file with the correct META data into
> the templates folder.

It sounds like exactly the kind of flexibility that opens up the Kolab 
server for external additions. I think it's very good.

Bo.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: signature
URL: <http://lists.kolab.org/pipermail/devel/attachments/20040122/f1e303f4/attachment.sig>