> 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/ > >
This would be great. But I think we hit this bug because of the fast moving target cherokee development and the .deb rules. If this gets implemented will be a great improvement for updates when using the lattest and greatest cherokee. But how many old config parameters versions will be keept, since cherokee still on heavy development ? For a .deb package the target is upgrading from debian lenny to squeeze ( cherokee 0.7.2 to 0.99.22 + updates prior freeze) and for Ubuntu from hardy (current LTS ) to next LTS ( 5.6 to I hope cherokee 1.0 ) or from ubuntu intrepid to jaunty to karmic ( cherokee versions 7.2 to 11.6 to 99.19 or 22 ) But here again: How many are using the debian/ubuntu oficial package version? and How many debian/ubuntu users are using a newer version from tar.gz or a deb from debian unstable or PPA ?? Yes we need to make it easy for users to upgrade but as an example with PostgreSQL, every distro upgrade we need to Dump and reload and check configs and API changes. When cherokee 1.0 comes to live I guess the use for cherokee will be more on the 1.0 version than the latest version. And here is when well see more cherokee installed that need backport for bugfixes than move to a newer version. Just like apache on debian/ubuntu is now. Saludos y Keep Cherokeeing ! Leonel _______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
