Skip to content

docs(#381): route bugsink alerts to discord #588

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
zgeoff merged 3 commits into from
Jul 16, 2026
Merged

docs(#381): route bugsink alerts to discord #588

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
db1b7cf
chore(#381): route bugsink alerts through resend smtp
zgeoff Jul 16, 2026
fe581c2
docs(#381): document discord webhook alert delivery
zgeoff Jul 16, 2026
2386a74
docs(#381): drop email alerting, document discord-only delivery
zgeoff Jul 16, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions apps/bugsink/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -38,6 +38,14 @@ move across with `bugsink-manage migrate_to_current_objectstorage`.
The R2 credentials also live on the `bugsink-r2` item in the `vers` 1Password vault. Unset the four
`R2_*` secrets and Bugsink falls back to storing files in the database.

## Alerts

New-issue, regression, and unmute alerts post to the alarms Discord channel: every project carries a
Discord messaging-service config pointing at the channel's incoming webhook (the
`bugsink-discord-webhook` item in the `vers` 1Password vault), and a new project gets the same
webhook added in its settings. No outgoing email is configured — alerting is webhook-only, and
per-project alert toggles live in each Bugsink project's settings.

## Housekeeping

The `.github/workflows/bugsink-vacuum.yml` workflow runs `bugsink-manage vacuum_files` monthly (and
Expand Down
4 changes: 3 additions & 1 deletion docs/architecture/deployment.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -291,7 +291,9 @@ fly secrets unset CREATE_SUPERUSER -a vers-bugsink

In the Bugsink UI, create one project per app, set each project's DSN as that app's `SENTRY_DSN`
secret, and set the web project's DSN as the `VITE_SENTRY_DSN` GitHub Actions variable plus a
`vers-app-web` secret of the same name. Mint an API token for CI source-map uploads
`vers-app-web` secret of the same name. Add the alarms Discord webhook (the
`bugsink-discord-webhook` item in the `vers` 1Password vault) as each project's messaging service,
so new-issue alerts reach the alarms channel. Mint an API token for CI source-map uploads
(`SENTRY_AUTH_TOKEN` GitHub secret) and one for the MCP server, added to the vault item as
`mcp-token`.

Expand Down
Loading