<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
</style>
</head>
<body class='hmmessage'>
Some random thoughts;<BR>
<BR>
Our config files serves three purposes, as it seems<BR>
a) specifying default values (though why on earth these are ever different from the hardcoded defaults escapes me)<BR>
b) specifying user overriding values<BR>
c) documenting available settings and their use<BR>
d) pushing changing defaults from the svn to installed instances<BR>
<BR>
I think we need to address these concerns separately.<BR>
<BR>
As I understand it, the config dir is so that we can<BR>
a) split humongous default config files into smaller ones<BR>
b) to be able to 'drop' module default config files into an installation without having to merge them into one big ini.<BR>
<BR>
I think the settings can be split thrice;<BR>
1) Stuff that _must_ be reconfigured per installation : ip number, shared ports and stuff like that. (All users, should need no expertise)<BR>
2) Stuff that _can_ be reconfigured per installation. (Special installation cases, needs some knowledge)<BR>
3) Stuff that _seldom_ needs tampering. (Advanced user, special installation)<BR>
<BR>
I would suggest we break free of the current mindset and think about how 1) could be solved differently.<BR>
<BR>
Maybe we should say "either supply these settings on the command line, or create an OpenSim.ini file, look at OpenSim.ini.example for an example"<BR>
<BR>
Most users would probably go a long way just by specifying the 1) params on the command line.<BR>
<BR>
Of course, the created OpenSim.ini should need to be a bare minimum, and would probably need to change very seldom.<BR> <BR>Best regards,<BR>Stefan Andersson<BR>Tribal Media AB<BR><BR><BR><BR> <BR>> Date: Sat, 14 Mar 2009 04:25:25 -0700<BR>> From: aerowolf@gmail.com<BR>> To: opensim-dev@lists.berlios.de<BR>> CC: opensim-users@lists.berlios.de<BR>> Subject: Re: [Opensim-dev] Round 2: Config changes preview<BR>> <BR>> because many people run their servers from inside their bin/<BR>> directory, and if it's named OpenSim.ini then any changes that are<BR>> made to that file will get overwritten (not just overridden) at the<BR>> next svn update.<BR>> <BR>> That's why it was renamed to OpenSim.ini.example -- originally, it was<BR>> set to OpenSim.ini, and that problem was pretty much the number one<BR>> support issue at that time.<BR>> <BR>> -Kyle H<BR>> <BR>> On Fri, Mar 13, 2009 at 5:00 PM, Paul Fishwick <fishwick@cise.ufl.edu> wrote:<BR>> > Justin Clark-Casey wrote:<BR>> >> To get OpenSim to run at all, the user still has to copy OpenSim.ini.example to OpenSim.ini (though it should be<BR>> >> possible to override this if config is supplied over the network).<BR>> ><BR>> > This may be a silly question, but is there some reason why we keep on<BR>> > suggesting<BR>> > that people copy OpenSim.ini.example to OpenSim.ini? Why not just make<BR>> > OpenSim.ini what happens to be in OpenSim.ini.example?<BR>> ><BR>> > -p<BR>> ><BR>> ><BR>> > Paul Fishwick, PhD<BR>> > Professor and Director, Digital Arts and Sciences Programs<BR>> > University of Florida<BR>> > Computer & Information Science and Eng. Dept.<BR>> > Bldg. CSE, Room 301<BR>> > P.O. Box 116120<BR>> > Gainesville, FL 32611<BR>> > Email: fishwick@cise.ufl.edu<BR>> > Phone: (352) 392-1414<BR>> > Fax: (352) 392-1220<BR>> > Web: http://www.cise.ufl.edu/~fishwick<BR>> ><BR>> > _______________________________________________<BR>> > Opensim-dev mailing list<BR>> > Opensim-dev@lists.berlios.de<BR>> > https://lists.berlios.de/mailman/listinfo/opensim-dev<BR>> ><BR>> _______________________________________________<BR>> Opensim-dev mailing list<BR>> Opensim-dev@lists.berlios.de<BR>> https://lists.berlios.de/mailman/listinfo/opensim-dev<BR></body>
</html>