On 2015-05-01 13:43, Andrew Stuart wrote:
[snip]
location / {
fastcgi_pass 10.9.1.201:8000;
fastcgi_index index.php;
fastcgi_keep_conn on;
include fastcgi_params;
fastcgi_param SCRIPT_FILENAME
/data/www/$fastcgi_script_name;
}
Hmm, I had to completely remove this bit from my configuration, or
nginx would hang.
It should be OK to remove, presuming you don’t want to send PHP
requests. nginx should ignore it unless you send an HTTP request to
the target location which now that I look at it, appears to be the
root route on the web server. I always have to fiddle with nginx
params to work out exactly what they are doing.
Yeah, you can remove that entirely, its there for talking to rump-php.
For reference, the nginx configuration I used for my benchmarks is:
worker_processes 1;
error_log stderr;
pid /tmp/nginx.pid;
user daemon daemon;
daemon off;
master_process off;
events {
worker_connections 128;
}
http {
include mime.types;
default_type application/octet-stream;
log_format main '$remote_addr - $remote_user [$time_local]
"$request" '
'$status $body_bytes_sent "$http_referer" '
'"$http_user_agent" "$http_x_forwarded_for"';
access_log /dev/null;
server {
listen 80;
server_name localhost;
location / {
root /data/www/static;
}
}
}
The Debian and NetBSD stock domUs use the exact same configuration.