All modules in OpenSim are independent of each other -- this is a very
strong principle of the architecture, as it allows people to do all
kinds of deployments. As such, each module has its own, independent
config section.
Vanilla installations (the ones that come in the .example files) do not
use that kind of flexibility, hence the impression that things are
redundant. But in non-vanilla installations that flexibility is
absolutely needed -- serving different services from different servers,
for example, and much more.
In any case, these .ini config files should be seen as "assembly level"
configurations. Ppl using OpenSim in specific deployment scenarios
should develop their own tools for generating these files. For example,
D2 does that.
On 5/13/2012 3:19 PM, Serendipity Seraph wrote:
You could do it as an Iron Python import file. With a little bit of work your
almost get it as clean as a Ruby DSL. :)
On May 13, 2012, at 8:58 AM, Melanie wrote:
Hi,
On 13/05/2012 10:36, Serendipity Seraph wrote:
Is there some way to get closer to obeying the DRY (don't repeat yourself)
principle in the config files? I see the same information (e.g. internet
address) repeated over and over again. This is a real pain when you need to
change something and it is not at all obvious whether some of the repeats mean
something different and should not be changed. I guess it is a property of
the old-school config file format. But whatever, it makes configuration and
especially changes to same messy and error-prone. Any good way to help it?
Old school, as opposed to what?
Melanie
_______________________________________________
Opensim-users mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/opensim-users
_______________________________________________
Opensim-users mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/opensim-users
_______________________________________________
Opensim-users mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/opensim-users
