Hot answers tagged django
What you are seeing is exactly how it is generally meant to work. A WSGI application should not care nor embed knowledge about where it is being mounted. In other words, you should not have 'api' as a prefix in urls.py. Why do you believe you need 'api' prefix in urls.py? UPDATE 1 You may be able to use: WSGIScriptAlias /api ...
I am skeptical this will work because I think you need to establish the https connection with the certificate of domain example-lab.org, which, it sounds like, would be a mismatched, or missing, certificate. Without a valid certificate, this would not be work. In other words: If you come in on https://mysite.example-lab.org/ (site you don't have cert for), ...
The "old" snmp stats export only values managed by the apps via the api. The new api is this one: http://uwsgi-docs.readthedocs.org/en/latest/Metrics.html that expose values via snmp as 126.96.36.199.4.1.35156.17.3.x in both cases you cannot walk but only get direct values
For Django 1.6> according to the changes... this settings are no longer necessary, https://code.djangoproject.com/wiki/BackwardsIncompatibleChanges#ChangedthewayURLpathsaredetermined I have commented out both the Path info and Script Name lines in fastcgi_params (in Debian-like cases) or in the nginx.conf (RHEL cases)
Only top voted, non community-wiki answers of a minimum length are eligible