14 messages in ru.sysoev.nginxRe: How to enable Nginx to serve PHP ...
FromSent OnAttachments
Mark AlanNov 3, 2008 6:29 am 
Edho P AriefNov 3, 2008 8:05 am 
mikeNov 3, 2008 9:39 am 
Mark AlanNov 3, 2008 10:06 am 
mikeNov 3, 2008 10:12 am 
Edho P AriefNov 4, 2008 5:32 am 
RoxisNov 4, 2008 5:41 am 
Edho P AriefNov 4, 2008 6:22 am 
Adam SetzlerNov 4, 2008 7:37 am 
mikeNov 4, 2008 11:23 am 
Adam ZellNov 4, 2008 12:23 pm 
Mark AlanNov 4, 2008 12:36 pm 
mikeNov 4, 2008 12:37 pm 
mikeNov 4, 2008 12:45 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: How to enable Nginx to serve PHP code/pages in UbuntuActions...
From:Adam Zell (zell@gmail.com)
Date:Nov 4, 2008 12:23:08 pm
List:ru.sysoev.nginx

Depending on you feel about closed source software, LiteSpeed handles PHP very well. The free version is limited to 150 concurrent connections but offers an optimized protocol.

http://www.litespeedtech.com/php-litespeed-sapi.html http://www.litespeedtech.com/products/webserver/download/

On Tue, Nov 4, 2008 at 11:23 AM, mike <mike@gmail.com> wrote:

don't use spawn-fcgi as i've had first hand problems with it not behaving properly.

instead if you won't use php-fpm, just make a script that basically does php-cgi -b $port (for TCP) - you can add in the environment variables and sudo to make it run better - i wound up creating upstart jobs in ubuntu (i think ~ 7.10 this is available)

this is my /etc/event.d/fastcgi-mike file:

start on runlevel 2 start on runlevel 3 start on runlevel 4 start on runlevel 5

stop on shutdown

env PHP_FCGI_MAX_REQUESTS=250 env PHP_FCGI_CHILDREN=5

respawn exec /usr/bin/sudo -u mike /usr/local/bin/php-cgi -b 10500

this allows for: - running as a different user id - one file per pool - auto startup on boot - "stop fastcgi-mike" and "start fastcgi-mike" for stopping/starting and it cleans it up properly - proper environment variable support, as opposed to my experience with spawn-fcgi ignoring PHP_FCGI_MAX_REQUESTS for example

php-fpm is the #1 option. #2 would be something like this (trigger it how you like but this provides all the options one could want)

On Tue, Nov 4, 2008 at 6:22 AM, Edho P Arief <ed@myconan.net> wrote:

On Tue, Nov 4, 2008 at 8:42 PM, Roxis <rox@list.ru> wrote:

On Tuesday 04 November 2008, Edho P Arief wrote:

I'm also waiting for the day it's merged with PHP core but currently it's the one of the best way to spawn and manage php-fcgi processes, the other (not as good as using php-fpm) is using spawn-fcgi provided by lighttpd (explained here http://wiki.codemongers.com/NginxFcgiExample )

Wha's the big deal about spawn-fcgi? Why is i better than an one-liner shell script?

I don't know really, perhaps because it works on most system?