zulip/puppet/zulip_internal/files/nginx/zulip-include-app.d/accept-loadbalancer.conf

# Configuration for making our app frontends accept the
# X-Forwarded-For header from our load balancers.  We need to update
# the IP addresses here whenever we add new loadbalancer machines.
real_ip_header X-Forwarded-For;
# lb0.zulip.net elastic IP
set_real_ip_from 10.0.0.95;
Clean up our nginx configuraiton to make better use of app.d. Now app.d is something that any app frontend will read, and we just have secondary manifests add additional files to the app.d directory for custom stuff. This fixes the issue that we were incorrectly including the lb0-related app configuration in the enterprise version. (imported from commit dec8dcdf2506b82e51186ff936c26dc1cd6cf61b) 2013-11-15 17:31:16 +01:00			`# Configuration for making our app frontends accept the`
			`# X-Forwarded-For header from our load balancers. We need to update`
			`# the IP addresses here whenever we add new loadbalancer machines.`
			`real_ip_header X-Forwarded-For;`
			`# lb0.zulip.net elastic IP`
[puppet] Update set_real_ip_from to use lb0's internal IP address. This is something we forgot to do in the VPC migration, so our IPs have all been the lb0 IP in our logs :(. (imported from commit 9d3fc69cf72a84f7bd7c54e50fb1e776a67d971f) 2013-12-03 19:20:46 +01:00			`set_real_ip_from 10.0.0.95;`