Klaas van Schelven db94c00a94 DJDT: pin at 5.2
'philosphofically' I prefer to keep my dev-deps in flux ('bleeding edge')
but since I barely use the DJDT I'd rather just pin it at a known-working
version.

Also: 6.0 introduces DB-models (for a debug tool) which I'm not a fan of.

Probably removing DJDT right after this, which would make this commit to
be a good point to revert to if we ever want to reintroduce it

See #168
2025-07-25 20:12:09 +02:00
2025-05-12 10:43:53 +02:00
2025-01-29 13:37:31 +01:00
2025-07-23 12:18:30 +02:00
2025-07-07 12:09:21 +02:00
2025-04-11 11:24:50 +02:00
2025-07-01 13:51:58 +02:00
2025-07-25 20:12:09 +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
Self-hosted Error Tracking
Readme 24 MiB
Languages
Python 80.4%
HTML 17.7%
CSS 0.9%
JavaScript 0.6%
Shell 0.3%
Other 0.1%