On Tuesday 02 September 2008, Alvaro Lopez Ortega said: > Beech Rintoul wrote: > > That being said, after some tweaking I moved 0.8x to our main > > port and except for a couple of minor issues (fixed) our users > > are very happy with it. I also removed the -devel version because > > I didn't feel it was needed anymore. We are also about to go into > > a code freeze for the new releases and I wanted to make sure > > Cherokee-0.8 was included. > > That's great news. > > > The only other request I've been getting is to make the admin > > install optional for users who already have cherokee installed or > > want to configure by hand. I haven't looked at that closely, but > > I don't remember seeing a --with-cherokee-admin knob. So that may > > take a bit of work. > > Yes, there is no parameter to omit the cherokee-admin installation. > There reason behind it is simply that the configuration file is not > meant to be modified by hand, so in 99% of the cases the final user > will need the interface. > > I can only think of two scenarios where cherokee-admin could be > skipped: Embedded systems and Cluster nodes.
We do have at least one user who is looking into doing exactly that (embedded). I think hes now using lighttpd, but he's very interested in Cherokee. BR > > Anyway, adding a configure.in parameter wouldn't hurt, so I suppose > it is worth adding even if it does not apply to the most common set > ups. -- --------------------------------------------------------------------------------------- Beech Rintoul - Sys. Administrator - [EMAIL PROTECTED] /"\ ASCII Ribbon Campaign | Alaska Paradise \ / - NO HTML/RTF in e-mail | 201 East 9Th Avenue Ste.310 X - NO Word docs in e-mail | Anchorage, AK 99501 / \ - Please visit Alaska Paradise - http://www.alaskaparadise.com --------------------------------------------------------------------------------------- _______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
