Welcome! Log In Create A New Profile

Advanced

Best way to handle preprod server_names

Greg
May 16, 2012 05:10AM
Hi,

I'm going to migrate a lots of vhosts from Squid+Apache2 to NginX, step
by step.
First step is to migrate just NginX and few static vhosts.

Actually there is ~600 domains x 5 vhosts + equivalent for preprod. So I
wrote a NginX vhost for ".mydomain1.com .mydomain2.com" and so on with
the 600 domains.

Question is, how the best practices to have this domains for our preprod
which looks like ".preprod.mydomain1.com" for each domains.

Preprod has specific config like gzip disabled (for internals purpose...).

Actually, prod's config looks like :
server {
server_name .mydomain1.com; # main domain
include /etc/nginx/domains.conf;
server_name_in_redirect off;
include common/prod.conf
}

And domains.conf :
server_name
..mydomain1.com
..mydomain2.com
....
;

Preprod could have this config :
server {
server_name .preprod.mydomain1.com; # main domain
include
/etc/nginx/preprod_domains.conf;
server_name_in_redirect off;
include common/preprod.conf
}

Which means (600 x 5 x 2) vhosts...

Is there a better way ?

--
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: 95
Record Number of Users: 6 on February 13, 2018
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready