John Hampton wrote: > Setting precedence via order of appearance in config file seems pretty > good, except it could get very confusing when using includes. > > Thinking about it some more, if order of appearance is used (and I'm not > against it) I definitely think that the higher precedence should be set > for things that appear later in the file.
I never would have considered an include causing a problem - good thinking! My personal thoughts would be that it isn't intuitive to make the precedence order first->lowest, last->highest. It seems more logical for items at the beginning of a config file to have higher precedence. As for ensuring that instructions in cherokee.conf can be overwritten, there are two options I can think of (if highest-to-lowest precedence is followed): (1) either included files are interpreted to always override the settings in cherokee.conf, or (2) the files can be included at the top of cherokee.conf. > The configuration syntax for Cherokee was one of the main > things that made me want to drop apache. Same here. Sincerely, Kurt McKee _______________________________________________ Cherokee mailing list [email protected] http://www.alobbs.com/cgi-bin/mailman/listinfo/cherokee
