On Tue, November 12, 2013 19:49, Stuart Henderson wrote: >> > On 13-11-11 07:06 PM, Stuart Henderson wrote: >> > >Help identify which ports currently rely on Apache from base, work out >> > >which ones can use nginx and move them across (updating READMEs etc where >> > >necessary), which can use apache2 from ports and move them across, and >> > >which (if any) won't work with either of these and require a port of >> > >the modified apache from base. > > Re this... > > We could do with some directory under /etc/nginx that ports can use as a > common place to install config fragments (that the use can then "include" in > nginx.conf), somewhat similar to /var/www/conf/modules.sample (but no > need for the symlink mechanism, having the user manually include them > makes more sense for nginx) and similar to debian's "sites-available"..
I thought symlink mechanism helps you to keep config fragment in sync, until you customize it. As for me, this should be done like php modules ini and apache module configs - with the help of symlinks and not copying this configuration chunks. This way or another, but we need some infrastructure for nginx config samples to encourage porters to test their webstuff with nginx without unneeded pain. Just my 0.02 RUR. > > Doesn't necessarily need to be in base's mtree (just using the same > directory in all ports would be enough), though it might make sense.. > >
