[Osiris-devel]version 1.5 base requirements

[B Potter]

> first i would like it if it ran fairly sensibly without a config file, or
> at least with the default config files.  i like it a lot when i can make a
> new app work immediately then then putz with it to learn the details of
> how it works.

agreed.  Brian and I spent a lot of time on the phone this weekend talking
about some of these kind of things.  I hate fucking with configs just to
get something functional.  Ideally, osiris will scan the whole box with
reasonable defaults if a) the config file isn't there, or b) it's the
default config file.

> 
> second, and this is mostly just a random thought, with the config
> structure below would it be worth usign the apache style config?  it's not
> that it's complicated or anything but they seem to server the same purpose
> and the apache syntax is already widely know and fairly widely used.  i
> guess the basic argument is "familiarity = good".
> 
I agree.  When I was talking to brian, I kept going back to the apache
configfile setup for examples..  It's a good setup as far as config's go,
and it's about the most universally known one out there.  It's verbose
enough you can read and troubleshoot without having a man page open, but
it's structured enough you can do lots of cutting and pasting if need be.
> 
> this might also allow cascaded settings so you could (thought you can't do
> this within apache):
> 
> <Directory /usr>
>   options	all,recursive
> 
>   <Directory /usr/local>
>     options	+follow_links
>     ignore	user( bob )
>     noentry	file( /usr/local/src )
>   </Directory>
> 
> </Directory>

I don't think "nesting" like this is too good of an idea.  In complicated
config files, it could make troubleshooting a pain.  Think "nested HTML
tables". ;)  

BTW: Spike has (will) be joining this list, and some verisign employees
may jump in as well.  The more eyes the better :)

later

bruce