Rodolfo Pilas wrote: > I wish to upgrade cherokee by the right way. > > a) Remove all previous installation > b) Compile and install new release > c) Configure with my requirements
For most versions you won't need to remove the previous version. The only scenario I can imagine in which that should be mandatory is a change a name convention of the plug-ins or something similar. There is a common mistake I know some people have suffered in the past. You must be careful with the --prefix parameter of configure. Remember to add it always to set the base path in which you want to install cherokee, by default it will use /usr/local. In my Debian system, I usually configure Cherokee with the following command like: ./configure --prefix=/usr --sysconfdir=/etc After that: "make && sudo make install" should be enough for upgrading to the newer version. > I wish to know if configuration files support "include" function. With > this function I would append "Include myconfig" to default site and > arrange cherokee.conf Yes, It does. Take a look at cherokee.conf. At the end, it includes a couple of directories and files. The idea is to put a new file for each virtual server in /etc/cherokee/sites-available and link it from /etc/cheorkee/sites-enabled if you want to activate it. It works in the same way for the modules: /etc/cherokee/mods-available. By the way, the Cherokee installation doesn't overwrite the configuration if there is already one in the system. So, on upgrading to a new version I can "make install" without troubles. > Additionaly, any suggestion to proper and authomatic upgrade is wellcomed. I'm not sure if I've answered your questions.. I hope so :-) -- Greetings, alo. http://www.alobbs.com _______________________________________________ Cherokee mailing list [email protected] http://www.alobbs.com/cgi-bin/mailman/listinfo/cherokee
