tags 822792 - pending thanks We had to pop this off because of other changes that needed to be released.
I've moved these specific changes into their own branch and plan to work on the change there until we have something ready with other upstream packages so that we can provide magical installations of web applications. > 1. After looking at conf/sites-available/default I noticed a > commented block handling .php files in there. > > Would a config file in apps.d be allowed to do exactly > that? Like apps.d/pkg_php-fpm.conf handling *.php > files? Nope! In fact, that's why I'm trying to be very strict with the format of these files. I don't want packages stepping on each other's toes. However... I've already covered this use case with conf.d. https://wiki.debian.org/Nginx/DirectoryStructure#appincludes "Example: /etc/nginx/conf.d/pkg_drupal8.conf" In this case, I'd say go ahead and provide /etc/nginx/conf.d/pkg_php-fpm.conf which would include "upstream _provider_php { ... }". This shouldn't be a problem unless someone tries to install multiple "php providers." I'd like to get something like _provider_php available via php-fpm as well as uwsgi-plugin-php. Doing it this way would reduce security, but I'm thinking it's to a very negligible degree and not very concerned. > 2. Do we have recommended naming for files added by the > local admin to apps.d? We could suggest custom_<foo>.conf. -- Michael Lustfield
