On Wed, Oct 19, 2016 at 2:47 AM, Olaf van der Spek <olafvds...@gmail.com> 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 this thread and in the documentation I linked to, I would be strongly opposed to anything extra created outside of the application files main path. Uncommenting this block means that we're saying sites-available/default should become a place for applications to put generic snippets and trust that we'll always make sure they work. We can't guarantee that the snippets will never change unexpectedly. Additionally, it's possible administrators would want to control/modify sites-avail/default and still want to include the sub-directory hosted applications. On top of that, it would be pushing the use of php-fpm where I would personally prefer uwsgi. I've already explained why I feel this way. Regardless, it shouldn't be my preference or anyone else's that gets to make that call. For my alternate suggestion, I offer the documentation that I wrote and linked to last night. ;) If you're looking for more immediate discussion, I am on #debian-nginx on OFTC as well as #nginx on freenode.