No OneTemporary
Actions

Size

2 KB

Subscribers

None

View Options

	diff --git a/site-modules/profile/templates/sentry/config.yml.erb b/site-modules/profile/templates/sentry/config.yml.erb
	index 64d5402b..e912cc71 100644
	--- a/site-modules/profile/templates/sentry/config.yml.erb
	+++ b/site-modules/profile/templates/sentry/config.yml.erb
	@@ -1,81 +1,82 @@
	# File managed by puppet (module profile::sentry), modifications will be lost!

	# While a lot of configuration in Sentry can be changed via the UI, for all
	# new-style config (as of 8.0) you can also declare values here in this file
	# to enforce defaults or to ensure they cannot be changed via the UI. For more
	# information see the Sentry documentation.

	###############
	# Mail Server #
	###############

	# mail.backend: 'smtp' # Use dummy if you want to disable email entirely
	mail.host: '<%= @mail_host %>'
	mail.port: 25
	-#mail.username: ''
	-#mail.password: ''
	-# mail.use-tls: false
	+mail.username: ''
	+mail.password: ''
	+mail.use-tls: false
	+
	# The email address to send on behalf of
	mail.from: '<%= @mail_from %>'

	# If you'd like to configure email replies, enable this.
	# mail.enable-replies: true

	# When email-replies are enabled, this value is used in the Reply-To header
	# mail.reply-hostname: ''

	# If you're using mailgun for inbound mail, set your API key and configure a
	# route to forward to /api/hooks/mailgun/inbound/
	# Also don't forget to set `mail.enable-replies: true` above.
	# mail.mailgun-api-key: ''

	###################
	# System Settings #
	###################

	# If this file ever becomes compromised, it's important to regenerate your a new key
	# Changing this value will result in all current sessions being invalidated.
	# A new key can be generated with `$ sentry config generate-secret-key`
	system.secret-key: '<%= @secret_key %>'

	# Sentry URL prefix
	system.url-prefix: 'https://<%= @vhost_name %>'

	# Sentry admin email address
	system.admin-email: '<%= @admin_email %>'

	# The ``redis.clusters`` setting is used, unsurprisingly, to configure Redis
	# clusters. These clusters can be then referred to by name when configuring
	# backends such as the cache, digests, or TSDB backend.
	# redis.clusters:
	# default:
	# hosts:
	# 0:
	# host: 127.0.0.1
	# port: 6379

	################
	# File storage #
	################

	# Uploaded media uses these `filestore` settings. The available
	# backends are either `filesystem` or `s3`.

	filestore.backend: 'filesystem'
	filestore.options:
	location: '/data/files'
	dsym.cache-path: '/data/dsym-cache'
	releasefile.cache-path: '/data/releasefile-cache'

	# filestore.backend: 's3'
	# filestore.options:
	# access_key: 'AKIXXXXXX'
	# secret_key: 'XXXXXXX'
	# bucket_name: 's3-bucket-name'

	system.internal-url-prefix: 'http://web:9000'
	symbolicator.enabled: true
	symbolicator.options:
	url: "http://symbolicator:3021"

	transaction-events.force-disable-internal-project: true

File Metadata

Mime Type: text/x-diff
Expires: Sat, Jun 21, 5:13 PM (1 w, 3 d ago)
Storage Engine: blob
Storage Format: Raw Data
Storage Handle: 3447338

No OneTemporaryActions

View Options

File Metadata

Event Timeline

No OneTemporary
Actions