Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Nginx 1.0.0 is out

nginx.org

Post reply on HN
Print view View original

11–20 of 77 posts

Re: Nginx 1.0.0 is out

#11

Post by sandGorgon »

josephb wrote: post #4
MichaelStubbs wrote: post #3

The changelog: http://nginx.org/en/CHANGES

Great to see a project that is constantly being worked on! Averaged more than 2 releases a month last year with bugfixes and features. An awesome web server.

until very recently, the SVN repo was not made available to the public. AFAIK, there is still no bug tracker.

Dont get me wrong, I have several production sites on nginx - but the development methodology makes me very nervous.

Cherokee has some of the same objectives as nginx (fast and lightweight) and has a very open development process.

Plus, the Cherokee Market is very cool (http://cherokee-market.com/) !

Re: Nginx 1.0.0 is out

#13

Post by dhimes »

pilif wrote: post #6

For me and this big PHP application of ours, switching from just Apache to nginx in front of Apache for PHP execution and serving the rest directly with nginx was the one optimization that brought the best bang for the buck over all the years. Memory usage went down drastically and response times got much better. Additionally, I personally much prefer the syntax of the nginx configuration file (though this really is…

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 profound technical insight on my part.

Re: Nginx 1.0.0 is out

#14

Post by justincormack »

kristofferR wrote: post #12

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.

There are a few features missing, arguably. There is only HTTP 1.0 not HTTP 1.1 support for the proxy module for example.

Re: Nginx 1.0.0 is out

#16

Post by njs12345 »

ez77 wrote: post #15

A bit off topic, please consider the following example in [1]: if ($args ~ post=140){ rewrite ^ http://example.com/ permanent; } Why is "^" used as a regex wildcard instead of ".*"? Thanks! [1] http://wiki.nginx.org/HttpRewriteModule

I think that regex matches any string as well - ^ simply matches the start of a line and all strings have a start.

It might also be more performant because the regex engine doesn't consume the whole string before finding a match..

Re: Nginx 1.0.0 is out

#18

Post by justincormack »

dhimes wrote: post #13
pilif wrote: post #6

For me and this big PHP application of ours, switching from just Apache to nginx in front of Apache for PHP execution and serving the rest directly with nginx was the one optimization that brought the best bang for the buck over all the years. Memory usage went down drastically and response times got much better. Additionally, I personally much prefer the syntax of the nginx configuration file (though this really is…

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 details on http://wiki.nginx.org/PHPFcgiExample

I found this much simpler than running nginx and apache...

Re: Nginx 1.0.0 is out

#19

Post by pilif »

dhimes wrote: post #13
pilif wrote: post #6

For me and this big PHP application of ours, switching from just Apache to nginx in front of Apache for PHP execution and serving the rest directly with nginx was the one optimization that brought the best bang for the buck over all the years. Memory usage went down drastically and response times got much better. Additionally, I personally much prefer the syntax of the nginx configuration file (though this really is…

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 time or interest to fix.

By now, there's PHP-FPM and fastcgi is much more common, so you could probably just hook php directly into nginx by now, but I didn't want to do experiments and I knew that apache worked, so that's what I used.

Just remember to turn off keep-alive in apache, btw.

Post reply on HN