zulip/zephyr/context_processors.py

from __future__ import absolute_import

from django.conf import settings
import simplejson

def add_settings(request):
    return {
        'full_navbar':   settings.FULL_NAVBAR,
    }

def add_metrics(request):
    return {
        'mixpanel_token': settings.MIXPANEL_TOKEN,
        'enable_metrics': simplejson.dumps(settings.DEPLOYED),
    }
Enable absolute imports. See PEP 328[1] for details. This feature was introduced in Python 2.5 and will become mandatory in Python 3. [1]: http://www.python.org/dev/peps/pep-0328 (imported from commit 7444eeba8a08d5f91b94c7921848f2274979bd76) 2013-04-23 18:51:17 +02:00			`from __future__ import absolute_import`

Hide most of the navbar on the deployed app (imported from commit 3b055588f7de805bf1b038f1bc6c03837eda010a) 2012-10-15 22:52:08 +02:00			`from django.conf import settings`
Add metrics variables to the template context via a context processor Wrapping render_to_response never actually worked correctly. On the login page, mixpanel_token would be missing, but we wouldn't get an error because it is surrounded by double quotes, which meant that it was still valid Javascript. (imported from commit 820ee42fab8f679983e5a3a4309a2feaf690f20f) 2013-06-17 18:01:22 +02:00			`import simplejson`
Hide most of the navbar on the deployed app (imported from commit 3b055588f7de805bf1b038f1bc6c03837eda010a) 2012-10-15 22:52:08 +02:00
context_processors: Rename misleadingly named unused parameter (imported from commit 45fcb3e349747f430372767c21a50660cbb19228) 2012-10-30 21:20:52 +01:00			`def add_settings(request):`
Use the obfuscated URLs The key property is that we never reveal the non-public directory name 4nrjx8cwce2bka8r to a not-logged-in user. This makes it less likely that random people from the Internet will download all our client code while we're still in private beta. (imported from commit 7428e847e0a1a34152cb6dc2b677c1b47290c202) 2012-10-17 20:34:38 +02:00			`return {`
			`'full_navbar': settings.FULL_NAVBAR,`
			`}`
Add metrics variables to the template context via a context processor Wrapping render_to_response never actually worked correctly. On the login page, mixpanel_token would be missing, but we wouldn't get an error because it is surrounded by double quotes, which meant that it was still valid Javascript. (imported from commit 820ee42fab8f679983e5a3a4309a2feaf690f20f) 2013-06-17 18:01:22 +02:00
			`def add_metrics(request):`
			`return {`
			`'mixpanel_token': settings.MIXPANEL_TOKEN,`
Disable the collection of metrics when not deployed We were using up a lot of events in our dev environments. (imported from commit 8413ecfa835cce0a231bdf437f37ad8cf12a9133) 2013-06-14 23:52:11 +02:00			`'enable_metrics': simplejson.dumps(settings.DEPLOYED),`
Add metrics variables to the template context via a context processor Wrapping render_to_response never actually worked correctly. On the login page, mixpanel_token would be missing, but we wouldn't get an error because it is surrounded by double quotes, which meant that it was still valid Javascript. (imported from commit 820ee42fab8f679983e5a3a4309a2feaf690f20f) 2013-06-17 18:01:22 +02:00			`}`