Bug#822792: (no subject)

2016-11-09 Thread Michael Lustfield
Sorry for the noise... should quiet down now. :(

Bug#822792: (no subject)

2016-11-09 Thread Michael Lustfield
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

Bug#822792: (no subject)

2016-10-29 Thread Michael Lustfield
After talking to Christos a bit, I think we'll be settling on "apps.d/" instead. I mistakingly pushed this change to our main branch instead of pushing to experimental. This will need to be done while working with other package maintainers to produce quality configurations which is mandatory for

Bug#822792: (no subject)

2016-09-29 Thread Michael Lustfield
Control: tags 822792 - wontfix > default-server-includes.d/*.conf It seems like an overly verbose name, but seems to also fit the use case. -- Michael Lustfield

Bug#822792: (no subject)

2016-09-04 Thread Mattia Rizzolo
On Sat, Jul 16, 2016 at 07:00:21PM -0700, Michael Lustfield wrote: > Using conf.d/* is a very common practice with web servers. Apache has this > exact same structure. Apache once had this structure, starting with 2.4 (Jessie) it changed to /etc/apache2/conf-available

Bug#822792: (no subject)

2016-07-16 Thread Michael Lustfield
Using conf.d/* is a very common practice with web servers. Apache has this exact same structure. Because of the way inheritance works in nginx configuration files, things that would typically work in apache do not work with Nginx. You're requesting we change away from how web server packages