Hi Antonio. On Fri, 10 Oct 2008 12:28:44 +0200, "Antonio Pérez" <[EMAIL PROTECTED]> wrote: > Hi Benjamin! > > On Fri, Oct 10, 2008 at 11:06 AM, Benjamin Podszun > <[EMAIL PROTECTED]> wrote: > >> On lighttpd I'm used to define a php fastcgi socket per vhost and > spawning >> the processes manually, giving each of them different UIDs/GIDs. Is > there a >> nice way to do that from the cherokee administration? The documentation >> talks only about the most basic setting for this scenario, but for > multiple >> unrelated vhosts I cannot (and don't want to) run the fastcgi processes >> with a) the same single user or b) the user of the webserver > > I think you can spawn php fascgi processes outside Cherokee, each with > his own socket, and define "Info sources" on Cherokee config that > "link" to those processes. Then, link php extension on each virtual > host to his "info source". > > I hope you understand what I mean. :)
Thanks for the answer. Yes, I understand what you mean. After all, that's exactly what I'm currently doing for lighttpd as well. Unfortunately this solution means that I cannot use cherokee-admin for fastcgi management (and my other thread/mail talks about the problem with managing more than one server, which again is not possible with the current way of setting cherokee up imo). I'm looking at cherokee currently for two reasons: - lighttpd has been very quiet lately (before they released 1.20 just now, so that point is moot) - The administration of cherokee seemed interesting and looked great at first Basically especially the administration stuff is something that sets cherokee apart for me. What I'm trying to say is, that I'd love to see an even more involved admin interface for tasks other than the basics (vhosts, rules). Speed between lighttpd and cherokee is comparable in my environment. Resource handling is fine with both of them. I'm fairly certain that improvements like this will come with the octality launch/success, since those guys probably need exactly the same stuff and much more. But until then the cherokee-admin interface provides no benefit for me (worse: It cannot be used at all and the config file syntax is - weird/again something new to learn) so the incentive to ditch lighttpd and move fades away. It would mean to relearn a new config syntax and to rewrite my scripts, with little (if at all) change for the better. I hope this doesn't offend anyone here, I'm really interested in the project and looking at the pace of development I'm amazed how much work you've done already. This mail is merely meant to be explain what would drag me to cherokee in an instant and why, what I feel is missing after playing around with a test installation for merely 1-2 days. Regards, Ben _______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
