On 08-sep-09, at 01:45, Gunnar Wolf wrote: > I will look into using ucf¹ (Update Configuration File: preserve user > changes to config files). The problem is that, in some cases, if we > don't automatically modify the user's configuration file, it will just > break the server. And Cherokee's configuration file is not meant to be > hand-editted except for specific cases. So I'd much rather avoid the > user doing so. > > Anyway, for most configfile-invasive changes we have had nice helpers > sent out by The Nice Cherokee Crew that have saved the day :-)
The plan is to make cherokee complain about old configuration files. It'll print an error message pointing the user to run cherokee-admin. Once cherokee-admin is launch it'll detect the configuration file version and automatically convert and save it. I suppose we could also add a new parameter to cherokee-admin, so it could do that from the command like. Something like: "cherokee-admin -- upgrade-config", so you could run it from the post-install script of the package. -- Octality http://www.octality.com/ _______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
