On 28 February 2013 06:04, amodpandey <nginx-fo...@nginx.us> wrote: > Let me put what I want to achieve. > > Before that I want to know what is this 'env' global directive for?
I don't know. The documentation suggests it's not going to solve the problem you want; but I've not used it. > I want to maintain a single set of configuration files for dev and prod. The > machines would have environment variable set ENV=dev or ENV=prod. Based on > the values of the ENV varibale I wanted to pick my upstream conf, either > upstream_dev.conf or upstream_prod.conf through 'include > upstream_$ENV.conf'. > > Please suggest an approach. Use something that helps you template your config files. Chef, puppet, Erb, Perl, bash - whatever works for you. [ However, I will suggest that rolling your own templating setup is a strong indicator of an inexperienced sysadmin; one who doesn't yet understand the value of consistency, the principle of least surprise, and why NIH is a Bad Thing. ] HTH, Jonathan -- Jonathan Matthews // Oxford, London, UK http://www.jpluscplusm.com/contact.html _______________________________________________ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx
