Fun Fact: I'm the downstream NGINX package maintainer in Ubuntu ;)
THIS SAID, 'changing' the documentation at this point would have to be bundled with a more important fix in Ubuntu to fix that. "Example Documentation" changes alone aren't enough to get it updated in an already-released release. This said... the "default" example in that package isn't exactly designed to be a "it will just work" all in one solution for PHP, it's designed as **guidance** not as explicit "confirmed to instantly work when you uncomment it" stuff. Part of that's just because the packages don't move all at the same speed, and part of that is because you really should be learning to handle your own configurations independently from the defaults which can change or get overwritten or any number of other things. This said, discussing downstream packaging differences vs. NGINX upstream here is not the discussion topic for nginx-devel. You can refer to the bug I linked already if you wish to continue this argument there. Thomas On 6/24/19 4:08 PM, Osman Kuzucu wrote: > Hello, > > As I said I am new to the Nginx dev world, and didn't even know there > was such website which I could keep track of the issues & additions & > removals. > > What you have shared there is the exact thing I was mentioning. I > honestly didn't tested the upstream version. > > What I did was pretty simple, create a fresh Ubuntu 18.04 x64 droplet > from the Digital Ocean. After initial SSH access, use the command > "sudo apt update", then "sudo apt upgrade" and finally "sudo apt > install nginx". That command order installed the nginx with the > default php7.0 setting and not with the php7.2. > > > > ------------------------------------------------------------------------ > *Gönderen:* Thomas Ward <[email protected]> > *Gönderildi:* 24 Haziran 2019 Pazartesi 19:26 > *Kime:* [email protected]; [email protected] > *Konu:* Re: Nginx Php7.2 update > > > Oops, I left original poster off my reply... heh. > > > (Reattaching them here for a reply-all) > > > > Thomas > > > > On 6/24/19 12:16 PM, Thomas Ward wrote: >> >> I don't think NGINX upstream provides this example you're referring to... >> >> >> Have you tested the upstream version and verified that this stanza is >> present there? (I could have SWORN there was a bug on this in Ubuntu >> [1], but it was NACK'd for stable-release-updating because it's not >> severe enough to warrant an SRU). >> >> >> Thomas >> >> >> [1]: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1831748 >> >> >> >> >> On 6/24/19 12:01 PM, Osman Kuzucu wrote: >>> Hello everyone, >>> >>> As I was configuring a new web server today, I have realized that >>> the latest nginx version (at least the one that is distributed by >>> the Digital Ocean) does have outdated configuration line for the PHP 7.2 >>> >>> The configuration line specifies the fastcgi line as "fastcgi_pass >>> unix:/var/run/php/php7.0-fpm.sock;" which causes "502 Bad Gateway" >>> errors, and if users are not careful about the issue, they might >>> have hard time debugging it. >>> >>> I suggest we change the default installation configuration to " >>> fastcgi_pass unix:/var/run/php/php7.2-fpm.sock;" so that if a user >>> installs Nginx and PHP7.2, they will automaticly be able to run PHP >>> files without any problem. >>> >>> Please excuse me if this has been addressed before. I tried to find >>> a way to push a change but I couldn't find a Github repo or >>> something similar, so I am sending this e-mail. >>> >>> Osman Kuzucu >>> >>> _______________________________________________ >>> nginx-devel mailing list >>> [email protected] <mailto:[email protected]> >>> http://mailman.nginx.org/mailman/listinfo/nginx-devel >> >> _______________________________________________ >> nginx-devel mailing list >> [email protected] <mailto:[email protected]> >> http://mailman.nginx.org/mailman/listinfo/nginx-devel
_______________________________________________ nginx-devel mailing list [email protected] http://mailman.nginx.org/mailman/listinfo/nginx-devel
