app/cloudfoundry_config.py

"""
Extracts cloudfoundry config from its json and populates the environment variables that we would expect to be populated
on local/aws boxes
"""

import os
import json


def extract_cloudfoundry_config():
    vcap_application = json.loads(os.environ.get('VCAP_APPLICATION'))
    os.environ['NOTIFY_ENVIRONMENT'] = vcap_application['space_name']
    os.environ['NOTIFY_LOG_PATH'] = '/home/vcap/logs/app.log'
Run on Paas 2016-12-08 16:50:37 +00:00			`"""`
			`Extracts cloudfoundry config from its json and populates the environment variables that we would expect to be populated`
			`on local/aws boxes`
			`"""`

			`import os`
			`import json`


			`def extract_cloudfoundry_config():`
bump utils to 13.1.0 brings in changes to allow logging json to sdout on cloudfoundry boxes 2017-01-09 19:14:04 +00:00			`vcap_application = json.loads(os.environ.get('VCAP_APPLICATION'))`
			`os.environ['NOTIFY_ENVIRONMENT'] = vcap_application['space_name']`
don't capture logs directly from stdout previously in run_app_paas.sh, we captured stdout from the app and piped that into the log file. However, this came up with a bunch of problems, mainly that exceptions with stack traces often weren't formatted properly, and kibana could not parse them instead, with the updated utils library, we can use that to log json straight to the appropriate directory directly. 2017-08-09 15:30:24 +01:00			`os.environ['NOTIFY_LOG_PATH'] = '/home/vcap/logs/app.log'`