[asterisk-dev] Asterisk 11 configuration files

[Tilghman Lesher]

On Mon, Aug 27, 2012 at 10:09 AM, Leif Madsen
<leif.madsen at asteriskdocs.org> wrote:
> On 23/08/12 10:35 PM, Paul Belanger wrote:
>>
>> I'm slowly starting to testing Asterisk 11 and noticed something about
>> our new modules config file names:
>>
>> chan_motif.so -> motif.conf
>>
>> and
>>
>> res_corosync.so -> res_corosync.conf
>> res_xmpp.so -> xmpp.conf
>>
>> When chan_dahdi was rewritten we moved to chan_dahdi.conf. Should we do
>> the same for chan_motif -> chan_motif.conf?
>>
>> Same for res_xmpp, we should move it to res_xmpp.conf.  This would line
>> up with the majority of resource modules config file names.  Like we did
>> for res_corosync.conf.
>>
>> Thoughts?
>
>
> As long as things are consistent, then I'm fine with either. It's the usage
> of motif.conf vs chan_dahdi.conf vs queues.conf that is bothersome.
>
> Lets come up with a standard for filenames, and switch everything over to
> using it. I think I would actually prefer things to be motif.conf,
> dahdi.conf, voicemail.conf, corosync.conf, etc... than to match up with the
> module name.
>
> For people implementing, no one really cares what the module name is.

It's additionally worth noting that several modules have multiple
configuration file names, e.g. queues.conf & queuerules.conf, sip.conf
& sip_notify.conf, iax.conf & iaxprov.conf.  You cannot go with a
standard of naming configuration files based upon their module names
AND BE CONSISTENT, if some modules have more than one standard
configuration file.

I agree with Leif, we probably shouldn't be naming configuration files
by their module names, and this is just one more reason.

-Tilghman