Skip to content

Error tracking: plain Sentry setup in docs, env and comments - #74

Merged
heliocosta-dev merged 1 commit into
mainfrom
error-tracking-generic
Oct 1, 2026
Merged

heliocosta-dev merged 1 commit into
mainfrom
error-tracking-generic

Conversation

@heliocosta-dev

Copy link
Copy Markdown
Member

Follow-up to #71. The error-tracking docs, .env.example (and the setup wizard's copy of it), code comments and test fixtures now describe plain Sentry SDK setup, naming no other tracker: DSN and source-map examples use <host>, and the privacy note says a tracker run by a third party is a sub-processor while one you host yourself is not.

No behaviour change. Locally: lint and typecheck clean; config 33, core 685, ses 160 (the .env.example mirror test included) and web 839 tests pass.

🤖 Generated with Claude Code

SELF_HOSTING.md, both self-hosting docs pages, .env.example and the setup
wizard's copy of it describe pointing SENTRY_DSN at a Sentry project, with
<host> in the DSN and source-map examples; code comments and test
fixtures name no particular tracker. Behaviour is unchanged.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@heliocosta-dev
heliocosta-dev merged commit 9bb104c into main Oct 1, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant