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