it works pretty nicely - spawning different fcgi for each vhost, - each fcgi process set runs as a different user - each vhost has its own php.ini file (which means its own open_base) - decent access control per vhost. - per vhost spawn-fcgi script (/etc/rc.d - FREEBSD) ... this needs some more testing though. the only downside is too many php-cgi processes. but running as different usesby cruelsymbol - How to...
Thanks I'll see if i can try that out using spawn-fcgi. I wish i could use php-fpm but seems to be too silent since php-5.2.9 n cos of that our policies does not allow us to use that on a production server.by cruelsymbol - How to...
thanks. i guess i'll just use snort to help me out this it then.by cruelsymbol - How to...
Is there anyway I can set different "open_basedir" for php for each virtual host configured using nginx. Similarly is there any way i can set different php "session.save_path" for each virtual host.by cruelsymbol - How to...
I went thru its wiki page but i didnt see any place where it explicitly limits POST. I think GET would also get affected by this. any thoughts?by cruelsymbol - How to...
Is there any nginx module I could use to limit the number of HTTP POSTs from users to a certain limit. Say like 100 per 10 seconds from a single IPby cruelsymbol - How to...