This patch introduces the following fixes to uWSGI config which
was not set up correctly to be used publicly (not behind a router,
load balancer, proxy like nginx etc.):
- Use `http` option for a front-proxy
- Set protocol back to `uwsgi` due to above
- Prevent forced socket binding to `uwsgi` due to protocol change
above (https://git.io/fj7Lw)
- Turn on "keep-alive" support
Should fixgetsentry/sentry-cli#40.
Django 1.7 already defaults to `True` for this and in Django 1.8, which
is what the latest Sentry uses, the option is removed and causes a DB
connection error so dropping it to fix git builds.
This removes auto-binding of various values (specified in config.yaml) when they're not actually configured. It ensures that these values can then be configured from the web UI as Sentry has intended.