Klaas van Schelven eea5f032e2 Clarified meaning of process_state.requesting_thread
(the now-removed 'treat as pid' was hallunicated by the bot; the
taken-from-sentry version missed the guard against -1)

> The index of the thread that requested a dump be written in the
> threads vector. [..] If the dump was not produced as a result of an exception
> [..] this field will be set to -1,
2025-11-12 21:33:18 +01:00
2025-09-09 16:10:44 +02:00
2025-11-11 10:01:23 +01:00
2025-11-11 15:25:51 +01:00
2025-11-09 20:58:39 +01:00
2025-11-11 15:25:51 +01:00
2025-11-12 21:03:03 +01:00
2025-09-26 15:01:55 +02:00
2025-10-01 17:13:39 +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-11-08 23:37:11 +01:00
2025-11-07 20:34:32 +01:00
2025-11-04 09:31:58 +01: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

Description
No description provided
Readme 6.2 MiB
Languages
Python 80.6%
HTML 17.5%
CSS 0.9%
JavaScript 0.6%
Shell 0.3%
Other 0.1%