> 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 I don't think it will be a bad commitment for > the future. > > > Can we remove the "wontfix" tag? > Your comments highly suggest to me, that this isn't a > wontfix anymore? > Almost. You convinced me, but I'd like to hear from at least Christos or Kartik on this matter. 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 * an entry in the nginx wiki about "best practices" and other info for writing their own * a well written readme file for this new directory that includes most of what's in the wiki * a decision about application server support * documentation for that app server * if uwsgi (my preference); we should also provide those configurations as well 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.
