Hi Lewis,
no, that won't cause double requests.
/myapp/current/blah.html
307 => /myapp/releases/1.2.0/blah.html
and from thereon (as we did not redirect internally, but rather
externally), any further accesses will happen unter the true "releases"
path (ideally, as relative URLs).
That's
Hi Lewis,
the idea is to have a deployment process that places apps or whatever
artifacts always in a certain distinct place that is determined once at
deployment time. This will determine the address where you can reach the
app in the namespace of NGINX. So, if the convention is to place an
