Bug#841230: [Pkg-nginx-maintainers] Bug#841230: Bug#841230: nginx: PHP 7 integration

2016-10-19 Thread Michael Lustfield
On Wed, Oct 19, 2016 at 2:47 AM, Olaf van der Spek wrote: > I was thinking, what about just uncommenting the PHP integration? > > When PHP isn't available it'd prevent PHP source from being served and > when PHP is available it easies setup. > > -- > Olaf Nope! Based on everything I've said in th

Bug#841230: [Pkg-nginx-maintainers] Bug#841230: Bug#841230: nginx: PHP 7 integration

2016-10-19 Thread Olaf van der Spek
I was thinking, what about just uncommenting the PHP integration? When PHP isn't available it'd prevent PHP source from being served and when PHP is available it easies setup. -- Olaf

Bug#841230: [Pkg-nginx-maintainers] Bug#841230: Bug#841230: nginx: PHP 7 integration

2016-10-19 Thread Michael Lustfield
I think it's supposed to be open-core, closed-modules. At least, that's what I remember hearing once. The source Debian uses is freely available here: http://nginx.org/en/download.html I have no interest in following nginx-plus so I really couldn't tell you what it's become.

Bug#841230: [Pkg-nginx-maintainers] Bug#841230: nginx: PHP 7 integration

2016-10-19 Thread Olaf van der Spek
2016-10-19 10:58 GMT+02:00 Michael Lustfield : > Ah, I'm guilty of a bad example! darnit :( Hehe.. BTW, is nginx going closed-source or dual-license? Seems I can't find the source anymore without providing an email address.

Bug#841230: [Pkg-nginx-maintainers] Bug#841230: nginx: PHP 7 integration

2016-10-19 Thread Michael Lustfield
Ah, I'm guilty of a bad example! darnit :( On Wed, Oct 19, 2016 at 12:26 AM, Olaf van der Spek wrote: > 2016-10-19 1:00 GMT+02:00 Michael Lustfield : >> However, that other line is an example of connecting to a TCP socket >> and I do not feel that it should be removed. I see (with painful >> freq

Bug#841230: [Pkg-nginx-maintainers] Bug#841230: nginx: PHP 7 integration

2016-10-19 Thread Olaf van der Spek
2016-10-19 1:00 GMT+02:00 Michael Lustfield : > However, that other line is an example of connecting to a TCP socket > and I do not feel that it should be removed. I see (with painful > frequency) users uncommenting that line in order to use apache to > serve php (or worse). As much as I'd prefer p

Bug#841230: [Pkg-nginx-maintainers] Bug#841230: nginx: PHP 7 integration

2016-10-18 Thread Michael Lustfield
I agree that using a unix socket is better than using a tcp socket and can support updating the ordering. I also see no reason not to update the example to point at the newer PHP socket location. However, that other line is an example of connecting to a TCP socket and I do not feel that it should

Bug#841230: nginx: PHP 7 integration

2016-10-18 Thread Olaf van der Spek
Package: nginx Severity: wishlist Dear Maintainer, > # fastcgi_pass unix:/var/run/php5-fpm.sock; Could you use PHP 7 in testing? And move it above the TCP line.. > fastcgi_pass 127.0.0.1:9000; Is the TCP line even needed / useful? It'd be simpler without it. Gr, Olaf -- System Informa