Gabriel Brown
913a57f8a6
The catalog in server/containers had drifted from the VPS. Eleven compose
files and twelve units no longer matched what runs, and two running
services, Gbrown_Agent and BillTracker, were missing. server/vps is now a
copy of the live files, and panama-server reads from it.
server/home holds the home server's services in the same shape. They still
run under Docker, so the podman units there are drafts for a later move, and
nothing installs from that tree. PostHog, Sentry and Plausible are checkouts
of upstream repositories. Only their local files are kept, next to an
UPSTREAM file naming the repository and the exact commit.
Every secret in both trees is a ${VAR} reference named in .env.example, or
CHANGE_ME in files that are not compose files. The live servers still hold
some of those values inline, so a live file can differ from its copy on
those lines alone. Existing .env.example files keep their comments, with new
keys appended at the end.
The ignore rules and the secrets contract now cover both trees, plus the
volume/ and volumes/ directories the home server uses.
151 lines
4.9 KiB
YAML
151 lines
4.9 KiB
YAML
# 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: 'smtp.usesend.gbrown.org'
|
|
mail.port: 587
|
|
mail.username: 'usesend'
|
|
mail.password: CHANGE_ME
|
|
# NOTE: `mail.use-tls` and `mail.use-ssl` are mutually exclusive and should not
|
|
# appear at the same time. Only uncomment one of them.
|
|
mail.use-tls: true
|
|
# mail.use-ssl: false
|
|
|
|
# NOTE: The following 2 configs (mail.from and mail.list-namespace) are set
|
|
# through SENTRY_MAIL_HOST in sentry.conf.py so remove those first if
|
|
# you want your values in this file to be effective!
|
|
|
|
# The email address to send on behalf of
|
|
mail.from: 'Sentry Admin <[email protected]>'
|
|
# mail.from: 'System Administrator <root@localhost>'
|
|
|
|
# The mailing list namespace for emails sent by this Sentry server.
|
|
# This should be a domain you own (often the same domain as the domain
|
|
# part of the `mail.from` configuration parameter value) or `localhost`.
|
|
mail.list-namespace: 'sentry.gbrown.org'
|
|
|
|
# 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 #
|
|
###################
|
|
|
|
# This is the main URL prefix where Sentry can be accessed.
|
|
# Sentry will use this to create links to its different parts of the web UI.
|
|
# This is most helpful if you are using an external reverse proxy.
|
|
system.url-prefix: https://sentry.gbrown.org
|
|
|
|
# Most of the time, this should NOT be changed. It's used for communication
|
|
# between containers. `web` is the container's name, and `9000` is the
|
|
# default port opened by the Sentry backend (this is NOT the public port).
|
|
#
|
|
# If you want to change the publicly exposed domain or port, you should change
|
|
# `system.url-prefix` above instead, along with `SENTRY_BIND` in `.env` file.
|
|
# Also see https://develop.sentry.dev/self-hosted/#productionalizing.
|
|
system.internal-url-prefix: 'http://web:9000'
|
|
|
|
# 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`
|
|
#
|
|
# If you are using SENTRY_SYSTEM_SECRET_KEY that is being set on your `.env` or `.env.custom` file,
|
|
# you should remove this line below as it won't be used anyway.
|
|
|
|
# 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:
|
|
# bucket_name: 's3-bucket-name'
|
|
|
|
filestore.profiles-backend: 's3'
|
|
filestore.profiles-options:
|
|
bucket_acl: "private"
|
|
default_acl: "private"
|
|
access_key: CHANGE_ME
|
|
secret_key: CHANGE_ME
|
|
bucket_name: "profiles"
|
|
region_name: "us-east-1"
|
|
endpoint_url: "http://seaweedfs:8333"
|
|
addressing_style: "path"
|
|
signature_version: "s3v4"
|
|
|
|
symbolicator.enabled: true
|
|
symbolicator.options:
|
|
url: "http://symbolicator:3021"
|
|
|
|
transaction-events.force-disable-internal-project: true
|
|
|
|
######################
|
|
# GitHub Integration #
|
|
######################
|
|
|
|
# Refer to https://develop.sentry.dev/integrations/github/ for setup instructions.
|
|
|
|
# github-login.extended-permissions: ['repo']
|
|
# github-app.id: GITHUB_APP_ID
|
|
# github-app.name: 'GITHUB_APP_NAME'
|
|
# github-app.client-id: 'GITHUB_CLIENT_ID'
|
|
|
|
#####################
|
|
# Slack Integration #
|
|
#####################
|
|
|
|
# Refer to https://develop.sentry.dev/integrations/slack/ for setup instructions.
|
|
|
|
# slack.client-id: <'client id'>
|
|
## If legacy-app is True use verification-token instead of signing-secret
|
|
|
|
|
|
#######################
|
|
# Discord Integration #
|
|
#######################
|
|
|
|
# Refer to https://develop.sentry.dev/integrations/discord/
|
|
|
|
# discord.application-id: "<application id>"
|
|
# discord.public-key: "<public key>"
|
|
|
|
###############
|
|
# Google Auth #
|
|
###############
|
|
|
|
# Refer to https://develop.sentry.dev/self-hosted/sso/#google-auth
|
|
|
|
# auth-google.client-id: "<client id>"
|