Hey,
we all know, nginx is far more tricky than apache, when it comes to write rules, even on those CMSs that we all know how to rewrite.
the problem here is that each domain/subdomain/subdirectory would need it's own set of rules set in the corresponding (user's / domain's) nginx.conf to function properly (or at all).
but what would happen when a sysadmin would need a rewrite_confs? because of either a faulty setting, or even performance improvement.
all those specific domain/user nginx rules will be overwritten.
we also cannot expect all the users on the server to write their own rewrite rules to replace their .htaccess, but that's a different issue.
so, maybe as partially suggested here, the Custom HTTPD Configurations should be renamed to something more general (because HTTPD is not necessarily used) and there have the user/domain specifics, which will not be rewritten.
maybe even add an additional:
to the user's nginx.conf template.
we all know, nginx is far more tricky than apache, when it comes to write rules, even on those CMSs that we all know how to rewrite.
the problem here is that each domain/subdomain/subdirectory would need it's own set of rules set in the corresponding (user's / domain's) nginx.conf to function properly (or at all).
but what would happen when a sysadmin would need a rewrite_confs? because of either a faulty setting, or even performance improvement.
all those specific domain/user nginx rules will be overwritten.
we also cannot expect all the users on the server to write their own rewrite rules to replace their .htaccess, but that's a different issue.
so, maybe as partially suggested here, the Custom HTTPD Configurations should be renamed to something more general (because HTTPD is not necessarily used) and there have the user/domain specifics, which will not be rewritten.
maybe even add an additional:
Code:
include /usr/local/directadmin/data/users/|USER|/nginx-|DOMAIN|.conf