Hi Byk,
Yes it’s just cloned last week and done installed using install.sh. Also adding a screenshot on what happened after I ran the restart command
###############
# Mail Server #
###############
# mail.backend: 'smtp' # Use dummy if you want to disable email entirely
mail.host: 'smtp'
# mail.port: 25
# mail.username: ''
# mail.password: ''
# mail.use-tls: false
# The email address to send on behalf of
# mail.from: 'root@localhost'
# 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 generate 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: 'e4U)KT0polj2>ccRJ-3gbeiiy-[xLoy#z60)0NasffXow\HUzo'
# 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`.
And the sentry.conf.py
from sentry.conf.server import * # NOQA
DATABASES = {
“default”: {
“ENGINE”: “sentry.db.postgres”,
“NAME”: “postgres”,
“USER”: “postgres”,
“PASSWORD”: “”,
“HOST”: “postgres”,
“PORT”: “”,
}
}
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
SENTRY_OPTIONS[“system.event-retention-days”] = int(
env(‘SENTRY_EVENT_RETENTION_DAYS’, ‘90’)
)
#########
Redis
#########
Generic Redis configuration used as defaults for various things including:
Buffers, Quotas, TSDB
SENTRY_OPTIONS[“redis.clusters”] = {
“default”: {
“hosts”: {0: {“host”: “redis”, “password”: “”, “port”: “6379”, “db”: “0”}}
}
}
# The digest backend powers notification summaries.
SENTRY_DIGESTS = **"sentry.digests.backends.redis.RedisBackend"**
**##############**
**# Web Server #**
**##############**
SENTRY_WEB_HOST = **"0.0.0.0"**
SENTRY_WEB_PORT = 9000
SENTRY_WEB_OPTIONS = {
**"memory-report"** : **False** ,
**# 'workers': 3, # the number of web workers**
}
**###########**
**# SSL/TLS #**
**###########**
**# If you're using a reverse SSL proxy, you should enable the X-Forwarded-Proto**
**# header and enable the settings below**
**# SECURE_PROXY_SSL_HEADER = ('HTTP_X_FORWARDED_PROTO', 'https')**
**# SESSION_COOKIE_SECURE =** **True**
**# CSRF_COOKIE_SECURE =** **True**
**# SOCIAL_AUTH_REDIRECT_IS_HTTPS =** **True**
**# End of SSL/TLS settings**
**############**
**# Features #**
**############**
SENTRY_FEATURES[ **"projects:sample-events"** ] = **False**
SENTRY_FEATURES.update(
{
feature: **True**
**for** feature **in** (
**"organizations:discover"** ,
**"organizations:events"** ,
**"organizations:discover-basic"** ,
**"organizations:discover-query"** ,
**"organizations:events-v2"** ,
**"organizations:global-views"** ,
**"organizations:integrations-issue-basic"** ,
**"organizations:integrations-issue-sync"** ,
**"organizations:invite-members"** ,
**"organizations:sso-basic"** ,
**"organizations:sso-rippling"** ,
**"organizations:sso-saml2"** ,
**"projects:custom-inbound-filters"** ,
**"projects:data-forwarding"** ,
