Best way to handle preprod server_names

[Greg]

Le 16/05/2012 18:47, B.R. a écrit :
> Hello,
>
> Typically, I would use one directory per host to serve content from 
> each domain and use one config file per generic type:

Hello,

thanks, but I can as I have to _migrate_ the actual config.
I'm going to generate server_name config in separates files, then 
include them in server {} config like :

server {
     server_name domain1.com; # main domain
     include prod_domains.conf;
     include commonrules.conf;
     include prod_rules.conf;
}
server {
     server_name preprod.domain1.com; # main domain
     include preprod_domains.conf;
     include commonrules.conf;
     include preprod_rules.conf;
}

But the server_names list will be huge...

-- 
Greg
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20120518/b7228091/attachment.html>