[Opensim-dev] Round 2: Config changes preview

[Sean Heavy]

+1 Melanie. Why are we trying to reinvent the wheel?

Since OpenSim, (also called the 3d web), is a server/service, similar to 
Apache or IIS, (the 2d web), can we just follow their example for 
configuration files? IIS has a web/gui based setup, which I assume is 
more than we are ready to do with Opensim at this stage. Apache has one 
config file, with embedded links to other config files as needed or 
wanted by the administrator. So, for those who want, one big config, for 
those who prefer multiple config files/folders, you can have it your way.

BTW, I have no Linux/MS bias here. I've been SysAdmin for both systems 
for a long time.

Peace,
Sean


Melanie wrote:
> Has anyone notices how impossibly complicated, complex and 
> unmaintainable this is going to become?
> Instead of demanding the user read a simple set of instructions, 
> then do the RightThing, you try to do all their thinking for them, 
> resulting in something that will make neither novice nor grid 
> operator happy.
>
> You are increasing, not decreasing, complexity and the effort to get 
> up and running.
> Rename, copy, multiple subdirectories, even I am hard put to see any 
> sense in that, and I'm a dev, for crying out loud!
>
> Melanie
>
> Mike Mazur wrote:
>   
>> Hi,
>>
>> On Sat, Mar 14, 2009 at 2:34 AM, Justin Clark-Casey
>> <jjustincc at googlemail.com> wrote:
>>     
>>> In this version I've done away with all the subdirectories.  There is now a simpler structure
>>>
>>> config/OpenSim.ini.example
>>> config/defaults
>>> config/override
>>>       
>> On first glance, it's not obvious how the config files in these
>> directories are treated. Is the defaults/ directory scanned for valid
>> .ini files which are then processed?
>>
>> The defaults/ directory contains scripting.ini.defaults. To enable
>> these settings, what should the user do? Rename to
>> defaults/scripting.ini, then edit? Is it necessary to copy to
>> override/scripting.ini and edit instead?
>>
>> In my opinion, having both a directory a *.ini.defaults extensions is
>> one too many. Perhaps we can get away with the two directories
>> containing only .ini files?
>>
>> config/OpenSim.ini.example
>> config/available/*.ini
>> config/override/*.ini
>>
>> Or we could have just one directory which contains *.ini.defaults (or
>> *.ini.example) files alongside *.ini files:
>>
>> config/OpenSim.ini.example
>> config/*.ini{,.defaults}
>>
>> To enable settings, just rename <whatever>.ini.defaults to <whatever>.ini.
>>
>> Mike
>>
>>