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 least Christos > or Kartik on this matter. Did they already answer? > As part of the resolution to this issue, I would expect to see, at a minimum: > > * a set of basic configuration files to be sent to other app packages #818585 - javascript-common: nginx snippet #838527 - letsencrypt.sh: Ship nginx snippet Instead of shipping them as snippets, they should probably end up in default-server-includes.d/*.conf ? I guess, default-server-includes.d/*.conf will have some 50-PACKAGENAME*.conf naming? So could you please advice on the right numbering for those two? So those two could start that set you requested. [...] > I'm entirely opposed to us creating the directory and letting it go > unmaintained, but you've convinced me we need to start looking into > this. Should we rename this bug to something indicating "we need to start looking into this" and remove the wontfix? Cheers Elrond
