21–30 of 77 posts
Nginx is awesome! I hope they'll start working on SPDY-support eventually now that they've reached a stable point with no major features missing.
I don't think nginx has support for websockets yet.
Earlier quoted context omitted.
Congratulations to the team indeed. I'm setting up my next project in this configuration as well and I've found nginx to be a very sweet server. I'll be serving a lot of javascript and css, but using php to handle the utility chores of accessing mysql and couchdb. Even though I'm keeping the apache back-end for this, I confess it's more out of comfort and laziness (and the rush to get it out) than because of some pro…
for me the reason to stay with an apache/mod_php backend was very bad experience I had with fastcgi back in the 2006/2007 area where I was using a lighttpd/fastcgi configuration. I've seen crashes in lighty, crashes in fastcgi and subtle differences in behavior between fastcgi and mod_php. FastCGI just wasn't a commonly used method of deployment back then, so there were for sure some bugs around that I didn't have ti…
Earlier quoted context omitted.
Congratulations to the team indeed. I'm setting up my next project in this configuration as well and I've found nginx to be a very sweet server. I'll be serving a lot of javascript and css, but using php to handle the utility chores of accessing mysql and couchdb. Even though I'm keeping the apache back-end for this, I confess it's more out of comfort and laziness (and the rush to get it out) than because of some pro…
It really is trivial to set up an fcgi process to run PHP directly from nginx. On the nginx side, something like my config: location ~ \.php { fastcgi_index index.php; include fastcgi_params; fastcgi_pass localhost:55155; fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name; } Then you just need to run php in fcgi daemon mode which is built in, use php-cgi -b localhost:55155 to match that setup... more de…
Nine years to get to version one. Happy birthday nginx.
Earlier quoted context omitted.
Congratulations to the team indeed. I'm setting up my next project in this configuration as well and I've found nginx to be a very sweet server. I'll be serving a lot of javascript and css, but using php to handle the utility chores of accessing mysql and couchdb. Even though I'm keeping the apache back-end for this, I confess it's more out of comfort and laziness (and the rush to get it out) than because of some pro…
for me the reason to stay with an apache/mod_php backend was very bad experience I had with fastcgi back in the 2006/2007 area where I was using a lighttpd/fastcgi configuration. I've seen crashes in lighty, crashes in fastcgi and subtle differences in behavior between fastcgi and mod_php. FastCGI just wasn't a commonly used method of deployment back then, so there were for sure some bugs around that I didn't have ti…
[1]: http://brainspl.at/articles/2006/08/23/nginx-my-new-favorite...
Does anybody know if/when Nginx will support HTTP 1.1? I'd love to be able to use Nginx as the frontend for WebSocket stuff.
Nine years to get to version one. Happy birthday nginx.
I've always wondered why there's such an extreme aversion for OSS to go to version 1.0, or to roll over to any major version, when commercial software has no problems going crazy with the versioning?
Additionally, marketing likes to see the major number change (the "X" in the X.Y.Z). I think the public does too. They feel like they're getting more bang for their buck.
Earlier quoted context omitted.
It really is trivial to set up an fcgi process to run PHP directly from nginx. On the nginx side, something like my config: location ~ \.php { fastcgi_index index.php; include fastcgi_params; fastcgi_pass localhost:55155; fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name; } Then you just need to run php in fcgi daemon mode which is built in, use php-cgi -b localhost:55155 to match that setup... more de…
A socket is probably faster.