I still can't find any difference between 0.5 and >=0.6 format other than readability. The nested structure remains much the same but <=0.5 was easier to read and easier to edit by hand.
The cumbersomeness to edit the /etc/cherokee/cherokee.conf by hand does not mean It can't be edited by hand. Tne cherokee admin tool is optional. I could some day prefer to just copy the /etc/cherokee/cherokee.conf from one server to another and do minor edits by hand. Something I wish Cherokee had is a directory named /etc/cherokee/conf.d and put small config files in it but in the meantime I can survive without includes. My point is: The /etc/cherokee/cherokee.conf is a configuration file and should live in the same place than the rest of the configuration files. I see no reason for moving it to /var/lib . Gunnar Wolf wrote: > I once mentioned the configuration should no longer be viewed as our > standard, Unixy, hand-editable-by-anybody configfile... And the more I > think about it, the more it convinces me. People, excuse me if I am > rehashing something that has already been debated, but... How does > moving the configuration to /var/lib/cherokee sound to you? > > Being in /var/lib/cherokee makes it clear it is not a file meant to be > edited by just anybody. And it makes it easier (and policy-wise, > feasible) to modify it programatically, either via cherokee-admin or > via migrator scripts. Besides, the configuration format has stabilized > (I hope we will never see another 05_to_06.py again!), and I guess > future changes could even be incorporated into cherokee-admin's > startup routines. > > Please comment. > > Greetings, > > -- Sandino Araico Sánchez http://sandino.net _______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
