Migrate from Bugsink to Epure (DSN cutover)
Leaving a one-container SQLite Bugsink box? Keep the Sentry SDK. Point dsn at Epure (app + PostgreSQL 16). Apache 2.0.
On this pageShowHide
If you outgrew SQLite-on-one-box, or you need Apache 2.0 instead of Polyform Shield, the cutover is still a DSN change. Fair compare: Epure vs Bugsink.
One container vs two
Footprint
- Bugsink
- 1 container (SQLite default)
- Epure
- 2 (app + PG 16)
License
- Bugsink
- Polyform Shield
- Epure
- Apache 2.0
SDK path
- Bugsink
- Sentry wire
- Epure
- Sentry wire
| Dimension | Bugsink | Epure |
|---|---|---|
| Footprint | 1 container (SQLite default) | 2 (app + PG 16) |
| License | Polyform Shield | Apache 2.0 |
| SDK path | Sentry wire | Sentry wire |
Stand up Epure
Installation, then compose up, health ok, create project, copy DSN.
Replace the Bugsink DSN
Leave packages unchanged. Only the DSN string moves.
Sentry.init({ dsn: "https://KEY@your-epure-host/PROJECT_ID", tracesSampleRate: 0, profilesSampleRate: 0, replaysSessionSampleRate: 0, replaysOnErrorSampleRate: 0 })
Verify
Known exception, then 202, then Issues: Verify. Then retire Bugsink when ready.
Stay on Bugsink when
You want SQLite in one process, Shield is acceptable, or you need their hosted EU SKU this week.