[asterisk-dev] Asterisk 11 configuration files

[Andrew Latham]

On Mon, Aug 27, 2012 at 1:12 PM, Tilghman Lesher <tilghman at meg.abyt.es> wrote:
> On Mon, Aug 27, 2012 at 12:10 PM, Andrew Latham <lathama at gmail.com> wrote:
>> On Mon, Aug 27, 2012 at 1:05 PM, Matthew  Jordan <mjordan at digium.com> wrote:
>>>
>>>
>>> ----- Original Message -----
>>>> From: "Tilghman Lesher" <tilghman at meg.abyt.es>
>>>> To: "Asterisk Developers Mailing List" <asterisk-dev at lists.digium.com>
>>>> Sent: Monday, August 27, 2012 11:57:11 AM
>>>> Subject: Re: [asterisk-dev] Asterisk 11 configuration files
>>>>
>>>>
>>>> Yes, it would be.  Please checkout minivm.conf.sample in the configs
>>>> directory.
>>>>
>>>
>>> I'm well aware of app_minivm and minivm.conf.sample.  Simply dropping the
>>> 'res_' or 'app_' seems to miss the point that Leif and others were shooting for.
>>>
>>> <quote>
>>> 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.
>>> <quote>
>>>
>>> It sounded as if folks were intending that configuration file names
>>> should mirror the functionality, and not the name of the module.
>>> The point is that going to that model - which is certainly simpler and
>>> more intuitive - has drawbacks.  That's all.
>>
>> Or as another option, define the config used in asterisk.conf or
>> module.conf for each module.
>
> Once you have multiple configuration files per module, though, that breaks.
>
> -Tilghman
>

Yup, thanks...  I was thinking of how other software does this...  Any
good correlations out there?


-- 
~ Andrew "lathama" Latham lathama at gmail.com http://lathama.net ~