Welcome! Log In Create A New Profile

Advanced

Re: Best way to handle preprod server_names

Greg
May 18, 2012 03:26AM
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
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Subject Author Posted

Best way to handle preprod server_names

Greg May 16, 2012 05:10AM

Re: Best way to handle preprod server_names

B.R. May 16, 2012 12:50PM

Re: Best way to handle preprod server_names

Greg May 18, 2012 03:26AM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 320
Record Number of Users: 8 on April 13, 2023
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready