Klaas van Schelven e10c1bf7ca Remove 'store_events' command
this command to store all events on the local filesystem was useful
while 'scaffolding'; getting my hands on some initial event-data in
the early days of Bugsink, but it was never meant as a permanent tool
2025-02-27 15:14:05 +01:00
2025-01-30 15:04:56 +01:00
2025-02-18 12:10:32 +01:00
2025-01-29 13:37:31 +01:00
2025-02-27 15:14:05 +01:00
2025-02-20 14:43:10 +01:00
2024-12-18 09:20:50 +01:00
2025-02-27 15:14:05 +01:00
2025-02-19 14:52:48 +01:00
2025-02-12 17:11:24 +01:00
2025-02-24 11:40:10 +01:00
2024-12-02 10:05:42 +01:00
2025-02-20 09:29:57 +01:00
2025-01-30 15:23:23 +01:00
2025-02-26 16:34:47 +01:00

Bugsink: Self-hosted Error Tracking

Bugsink offers real-time error tracking for your applications with full control through self-hosting.

Screenshot

This is what you'll get:

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={{ random_secret }} \
  -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 25 MiB
Languages
Python 80.8%
HTML 17.3%
CSS 0.9%
JavaScript 0.6%
Shell 0.3%
Other 0.1%