generate-py.sh

#!/bin/bash

REDIS_HOST=`echo $VCAP_SERVICES | jq '.["p-redis"]' | jq '.[0].credentials.host'`
REDIS_PWD=`echo $VCAP_SERVICES | jq '.["p-redis"]' | jq '.[0].credentials.password'`
REDIS_PORT=`echo $VCAP_SERVICES | jq '.["p-redis"]' | jq '.[0].credentials.port'`
REDIS_URI=redis://:$REDIS_PWD@$REDIS_HOST:$REDIS_PORT/0
echo "host: ${REDIS_HOST}, port: ${REDIS_PORT}, pwd: ${REDIS_PWD}"
echo $REDIS_URI
cat > .sentry/sentry.conf.py << EOF
# This file is just Python, with a touch of Django which means
# you can inherit and tweak settings to your hearts content.
print "Hello World"
from sentry.conf.server import *
import os.path
import dj_database_url
CONF_ROOT = os.path.dirname(__file__)
DATABASES['default'] = dj_database_url.config(default='$DATABASE_URL')
print DATABASES
# You should not change this setting after your database has been created
# unless you have altered all schemas first
SENTRY_USE_BIG_INTS = True
# If you're expecting any kind of real traffic on Sentry, we highly recommend
# configuring the CACHES and Redis settings
###########
# General #
###########
# Instruct Sentry that this install intends to be run by a single organization
# and thus various UI optimizations should be enabled.
SENTRY_SINGLE_ORGANIZATION = True
DEBUG = False
#########
# Cache #
#########
# Sentry currently utilizes two separate mechanisms. While CACHES is not a
# requirement, it will optimize several high throughput patterns.
# If you wish to use memcached, install the dependencies and adjust the config
# as shown:
#
#   pip install python-memcached
#
# CACHES = {
#     'default': {
#         'BACKEND': 'django.core.cache.backends.memcached.MemcachedCache',
#         'LOCATION': ['127.0.0.1:11211'],
#     }
# }
# A primary cache is required for things such as processing events
SENTRY_CACHE = 'sentry.cache.redis.RedisCache'
#########
# Queue #
#########
# See https://docs.sentry.io/on-premise/server/queue/ for more
# information on configuring your queue broker and workers. Sentry relies
# on a Python framework called Celery to manage queues.
BROKER_URL = "redis://:" + ${REDIS_PWD} + "@" + ${REDIS_HOST} + ":" + str(${REDIS_PORT}) + "/0"
###############
# Rate Limits #
###############
# Rate limits apply to notification handlers and are enforced per-project
# automatically.
SENTRY_RATELIMITER = 'sentry.ratelimits.redis.RedisRateLimiter'
##################
# Update Buffers #
##################
# Buffers (combined with queueing) act as an intermediate layer between the
# database and the storage API. They will greatly improve efficiency on large
# numbers of the same events being sent to the API in a short amount of time.
# (read: if you send any kind of real data to Sentry, you should enable buffers)
SENTRY_BUFFER = 'sentry.buffer.redis.RedisBuffer'
##########
# Quotas #
##########
# Quotas allow you to rate limit individual projects or the Sentry install as
# a whole.
SENTRY_QUOTAS = 'sentry.quotas.redis.RedisQuota'
########
# TSDB #
########
# The TSDB is used for building charts as well as making things like per-rate
# alerts possible.
SENTRY_TSDB = 'sentry.tsdb.redis.RedisTSDB'
###########
# Digests #
###########
# The digest backend powers notification summaries.
SENTRY_DIGESTS = 'sentry.digests.backends.redis.RedisBackend'
##############
# Web Server #
##############
# If you're using a reverse SSL proxy, you should enable the X-Forwarded-Proto
# header and uncomment the following settings
# SECURE_PROXY_SSL_HEADER = ('HTTP_X_FORWARDED_PROTO', 'https')
# SESSION_COOKIE_SECURE = True
# CSRF_COOKIE_SECURE = True
# If you're not hosting at the root of your web server,
# you need to uncomment and set it to the path where Sentry is hosted.
# FORCE_SCRIPT_NAME = '/sentry'
SENTRY_WEB_HOST = '0.0.0.0'
SENTRY_WEB_PORT = $PORT
SENTRY_WEB_OPTIONS = {
#    'workers': 3,  # the number of web workers
#    'protocol': 'uwsgi',  # Enable uwsgi protocol instead of http
}
EOF