[asterisk-gui] Should the GUI write to actual config files?

Brandon Kruse bkruse at digium.com
Thu Apr 5 12:31:01 MST 2007


Alexandre, try this command

cd /etc/asterisk ; for i in `ls` ; do cat $i | grep -v ';' > $i.bak ; mv 
$i.bak $i; done

:]

-bkruse

Oh, and to Tzafrir,

I totally agree with you, i meant for both config files, which you can 
do, and I agree
it is probably not the best way to do it.

Alexandre Moutinho Santos wrote:
> Hi Brandon,
> I once used the Advanced option on the GUI to configure sip.conf and
> what I noticed was that the GUI added the options available there (blank
> or not) to the end of sip.conf. As I had installed the sample sip.conf
> it was a bit messy (visually speaking :-) ).
> My opinion would be to replace all configuration files (the ones that
> are installed with make samples) with simpler ones, without all those
> examples and comments but with the basic functionality.
>
> Alex
>
> Brandon Kruse escreveu:
>   
>> Hey guys, brandon again.
>>
>>
>> I was wondering about what your experiences/ideas are
>> about the GUI and writing to config files.
>>
>> Ever written things by hand and had them erased?
>>
>> You think we should have like configname.gui.conf and
>> then include that in configname.conf (especially for
>> extensions.conf if nothing else)
>>
>>
>> Lets hear your thoughts......
>>
>> -bkruse
>> _______________________________________________
>> --Bandwidth and Colocation provided by Easynews.com --
>>
>> asterisk-gui mailing list
>> To UNSUBSCRIBE or update options visit:
>>   http://lists.digium.com/mailman/listinfo/asterisk-gui
>>     
>
>   
> ------------------------------------------------------------------------
>
> _______________________________________________
> --Bandwidth and Colocation provided by Easynews.com --
>
> asterisk-gui mailing list
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-gui



More information about the asterisk-gui mailing list