Re: Mechanism to avoid restarting nginx upon every change

2017-04-11 Thread Ajay Garg
wn the old ones. >>> There's absolutely no downtime involved in this process. >>> >>> >>> From: nginx on behalf of Ajay Garg < >>> ajaygargn...@gmail.com> >>> Reply-To: "nginx@nginx.org" >>> Date: Sunday, 9

Re: Mechanism to avoid restarting nginx upon every change

2017-04-11 Thread B.R. via nginx
tart >> new workers, and gracefully shut down the old ones. >> There's absolutely no downtime involved in this process. >> >> >> From: nginx on behalf of Ajay Garg < >> ajaygargn...@gmail.com> >> Reply-To: "nginx@nginx.org" >>

Re: Mechanism to avoid restarting nginx upon every change

2017-04-10 Thread Alex Samad
s. > There's absolutely no downtime involved in this process. > > > From: nginx on behalf of Ajay Garg < > ajaygargn...@gmail.com> > Reply-To: "nginx@nginx.org" > Date: Sunday, 9 April 2017 at 15.55 > To: "nginx@nginx.org" > Subject: Mechanism

Re: Mechanism to avoid restarting nginx upon every change

2017-04-10 Thread B.R. via nginx
the configuration, start >> new workers, and gracefully shut down the old ones. >> There's absolutely no downtime involved in this process. >> >> >> From: nginx on behalf of Ajay Garg < >> ajaygargn...@gmail.com> >> Reply-To: "nginx@ngi

Re: Mechanism to avoid restarting nginx upon every change

2017-04-09 Thread Ajay Garg
ime involved in this process. > > > From: nginx on behalf of Ajay Garg < > ajaygargn...@gmail.com> > Reply-To: "nginx@nginx.org" > Date: Sunday, 9 April 2017 at 15.55 > To: "nginx@nginx.org" > Subject: Mechanism to avoid restarting nginx upon ev

Re: Mechanism to avoid restarting nginx upon every change

2017-04-09 Thread Lucas Rolff
ilto:nginx-boun...@nginx.org>> on behalf of Ajay Garg mailto:ajaygargn...@gmail.com>> Reply-To: "nginx@nginx.org<mailto:nginx@nginx.org>" mailto:nginx@nginx.org>> Date: Sunday, 9 April 2017 at 15.55 To: "nginx@nginx.org<mailto:nginx@nginx.org>" mai

Mechanism to avoid restarting nginx upon every change

2017-04-09 Thread Ajay Garg
Hi All. We are wanting to implement a solution, wherein the user gets proxied to the appropriate local-url, depending upon the credentials. Following architecture works like a charm (thanks a ton to fran...@daoine.org, without whom I would not have been able to reach here) ::