Klaas van Schelven a58ceba31f transaction: use connection.vendor instead of settings.DATABASES engine check
connection.vendor reflects the actual backend of the connection in use,
not just the ENGINE string in global settings. This makes the check more
robust when multiple databases are configured (e.g. main DB on MySQL,
snappea DB on SQLite). The sqlite-specific handling now only applies to
the relevant connection.

See #117
2025-09-05 23:15:33 +02:00
2025-09-04 11:48:12 +02:00
2025-07-29 12:53:10 +02:00
2025-09-04 13:20:22 +02:00
2025-09-02 13:30:09 +02:00
2025-09-05 22:47:22 +02:00
2025-09-05 22:47:22 +02:00
2025-09-04 13:20:22 +02:00
2025-09-05 22:47:22 +02:00
2025-09-05 22:47:22 +02:00
2025-09-05 22:47:22 +02:00
2025-08-30 15:10:50 +02:00
2025-04-11 11:24:50 +02:00
2025-09-05 09:54:32 +02:00
2025-08-30 15:10:50 +02:00
2025-09-04 11:48:12 +02:00
2025-07-29 12:53:10 +02:00
2025-01-30 15:23:23 +01:00
2025-02-26 16:34:47 +01:00

Bugsink: Self-hosted Error Tracking

Screenshot

Screenshot

Installation & docs

The quickest way to evaluate Bugsink is to spin up a throw-away instance using Docker:

docker pull bugsink/bugsink:latest

docker run \
  -e SECRET_KEY=PUT_AN_ACTUAL_RANDOM_SECRET_HERE_OF_AT_LEAST_50_CHARS \
  -e CREATE_SUPERUSER=admin:admin \
  -e PORT=8000 \
  -p 8000:8000 \
  bugsink/bugsink

Visit http://localhost:8000/, where you'll see a login screen. The default username and password are admin.

Now, you can set up your first project and start tracking errors.

Detailed installation instructions are on the Bugsink website.

More information and documentation

S
Description
Self-hosted Error Tracking
Readme 28 MiB
Languages
Python 81.9%
HTML 16.3%
CSS 0.8%
JavaScript 0.6%
Shell 0.3%
Other 0.1%