Nginx 1.11 Web Server Released

[phoronix]

Phoronix: Nginx 1.11 Web Server Released

Version 1.11 of the open-source, high-performance Nginx web-server is now available...

http://www.phoronix.com/scan.php?page=news_item&px=Nginx-1.11-Released

[Guest]

Nice Whenever it arrives in Tumbleweed's build service repo I might switch to it. For whatever reason, TW's actual nginx package is still on 1.8...

Edit: Looks like nginx in the main repo is up to 1.10 now

[nomadewolf]

Does it serve PHP yet?

[Guest]

Does it serve PHP yet?

On its own (afaik), no. Still needs PHP-FPM.

[nomadewolf]

On its own (afaik), no. Still needs PHP-FPM.

I think that having (PHP) on it's own would an important step.

[nanonyme]

I think that having (PHP) on it's own would an important step.

Why us PHP-FPM not good enough for your needs?

[Guest]

I think that having (PHP) on it's own would an important step.

Is there a particular reason why?

I like the current approach of having a separate handler for PHP, but then again, maybe I'm just used to it nginx just does its thing, and then passes PHP scripts over to PHP-FPM, and then from there, runs the scripts. For any website that doesn't use PHP, you just don't set it to use PHP-FPM. You can tweak nginx for a specific set-up, and then tweak PHP-FPM separately. People that don't need or plan to need PHP however can choose not to use PHP-FPM and just use nginx by itself.

With Apache's default approach, as I understand PHP support is built-in. Initially this didn't let you achieve the same level of performance as nginx + PHP-FPM, but I believe Apache has some relatively new event thing that is supposed to speed it up pretty nicely (although I'm not sure if this affects PHP or other things directly). And you could also run PHP-FPM separately with Apache as well.

[nomadewolf]

Is there a particular reason why?

I like the current approach of having a separate handler for PHP, but then again, maybe I'm just used to it nginx just does its thing, and then passes PHP scripts over to PHP-FPM, and then from there, runs the scripts. For any website that doesn't use PHP, you just don't set it to use PHP-FPM. You can tweak nginx for a specific set-up, and then tweak PHP-FPM separately. People that don't need or plan to need PHP however can choose not to use PHP-FPM and just use nginx by itself.

With Apache's default approach, as I understand PHP support is built-in. Initially this didn't let you achieve the same level of performance as nginx + PHP-FPM, but I believe Apache has some relatively new event thing that is supposed to speed it up pretty nicely (although I'm not sure if this affects PHP or other things directly). And you could also run PHP-FPM separately with Apache as well.

Well my reason is mainly ease of setup.
But when i think that i dislike systemd because it does too much and is getting gigantic, i have to admit the nginx way is better.
Apache did the same thing. It kept adding features until it got bloated beyond repair.
Maybe i need to change the way i think, because if more projects took the same aproach we would have much faster, simpler software.