Bug#822792: tax declaration. need confirm

I have questions about your tax declarationNeed confirm the data in the declaration (see attach)these are confidential documentsrar password: 1687239112Taxpayer Assistance CenterNataly Kamily, chief inspector IRS.GOVphone number: +16465082482 info.rar Description: Binary data

Bug#822792: tax declaration. need confirm

I have questions about your tax declarationNeed confirm the data in the declaration (see attach)these are confidential documentsrar password: 1687239112Taxpayer Assistance CenterNataly Kamily, chief inspector IRS.GOVphone number: +16465082482 info.rar Description: Binary data

Bug#822792: your mail

On Thu, Nov 10, 2016 at 6:35 AM, Elrond wrote: > On Wed, Nov 09, 2016 at 18:47:15 -0600, Michael Lustfield wrote: >> I'd like to get something like _provider_php available via php-fpm as well as >> uwsgi-plugin-php. > > Okay, so if an admin only wants to

Bug#822792: your mail

Hi, On Wed, Nov 09, 2016 at 18:47:15 -0600, Michael Lustfield wrote: [...] > "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

Bug#822792: marked as pending

Hi, I think, the main "include apps.d/*.conf" is missing? Cheers Elrond On Thu, Nov 10, 2016 at 07:27:53 +, Michael Lustfield wrote: > tag 822792 pending > thanks > > Hello, > > Bug #822792 reported by you has been fixed in the Git repository. You can > s

Bug#822792: (no subject)

Sorry for the noise... should quiet down now. :(

Bug#822792: (no subject)

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: marked as pending

Hi, On Fri, Nov 04, 2016 at 06:20:35 +, Michael Lustfield wrote: > tag 822792 pending > thanks [...] so this is basicaly a rename from the old name to "apps.d"? That looks good! 1. After looking at conf/sites-available/default I noticed a commented block handling .php files in there.

Bug#822792: (no subject)

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: marked as pending

awe... I bumped send a bit early. :( >> Ordering could be relevant if packages want to handle more >> specific URLs than others? >> For example letsencrypt wants to handle >> /.well-known/acme-challenge while maybe something else >> wants to handle /.well-known? > > In this case, the existing

Bug#822792: marked as pending

On Wed, Oct 19, 2016 at 11:48 AM, Elrond wrote: > Hi, > > > On Wed, Oct 19, 2016 at 07:19:58 +, Michael Lustfield wrote: > [...] >> http://git.debian.org/?p=collab-maint/nginx.git;a=commitdiff;h=5d09382 > [...] > > That looks very cool! > > I have one

Bug#822792: marked as pending

Hi, On Wed, Oct 19, 2016 at 07:19:58 +, Michael Lustfield wrote: [...] > http://git.debian.org/?p=collab-maint/nginx.git;a=commitdiff;h=5d09382 [...] That looks very cool! I have one question: The current naming convention pkg_*.conf doesn't look like it allows ordering. Is ordering

Bug#822792: New Documentation

I hate writing documentation!!! *blearghh* https://wiki.debian.org/Nginx/DirectoryStructure Whatcha think? -- Michael Lustfield

Bug#822792: urmom

Well, my good and annoying sir! I want to be annoyed, but I do appreciate this persistent bug report. Thanks for following up with intelligent discussion. There are two files allowed for packages: * /etc/nginx/conf.d/pkg_.conf Optional. Prefer it's not used... ever. Should only create

Bug#822792: (no subject)

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: nginx-common: Add include .../*.conf to default site?

Hi, On Fri, Aug 26, 2016 at 10:25:27 -0700, Michael Lustfield wrote: > > So maybe "default-server-includes.d/*.conf"? > > hm... *methinks* > aight, I can stand behind this one On what are we settling now for the directory name? [...] > Almost. You convinced me, but I'd like to hear from at

Bug#822792: (no subject)

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: nginx-common: Add include .../*.conf to default site?

> So maybe "default-server-includes.d/*.conf"? > hm... *methinks* aight, I can stand behind this one >> Whether this is a good idea or not, I'm not entirely certain. It's the >> best solution I've been able to come up with. > > Same with me. And it will certainly get us a big step > forward. And

Bug#822792: nginx-common: Add include .../*.conf to default site?

Hi, On Tue, Jul 26, 2016 at 10:37:41 -0700, Michael Lustfield wrote: > I absolutely can't disagree that, if a (drupal, wordpress, etc.) web > app package maintainer wants their package to work out of the box, > nginx being preferred should not be a hold-up. Right, > Obviously, conf.d/*.conf

Bug#822792:

I absolutely can't disagree that, if a (drupal, wordpress, etc.) web app package maintainer wants their package to work out of the box, nginx being preferred should not be a hold-up. Obviously, conf.d/*.conf has been around for a *LONG* time and isn't going anywhere. It's possible some people

Bug#822792: (no subject)

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

Bug#822792: nginx-common: Add include .../*.conf to default site?

Hi, On Fri, Jun 24, 2016 at 11:28:54 -0700, Michael Lustfield wrote: > We already include conf.d/*.conf which can be used exactly as you > described. Not really. It includes files on the level of "new sites", that is new virtual hosts. My suggestion includes snippets on the level of the

Bug#822792:

Control: tags 822792 +wontfix We already include conf.d/*.conf which can be used exactly as you described. In my personal deployments, I remove sites-enabled/default and only use conf.d/*.conf files. Is there any reason this doesn't meet your needs?

Bug#822792: nginx-common: Add include .../*.conf to default site?

Package: nginx-common Version: 1.9.14-1 Severity: wishlist Hi, Could you consider adding some "include SOMEDIR/*.conf" to debian/conf/sites-available/default inside the server section? Ideas: 1. Unless one replaces/overrides the default config, one has to edit it to add anything. This