Klaas van Schelven 7849cf27b5 'recommended' setup: point slightly less strongly in this direction
I'm personally a big fan of the single-server setup, but the reality is that a lot of
people like Docker, and we don't want to scare people away from the Docker setup either
(especially since it's pretty good these days)
2024-12-02 16:25:00 +01:00
2024-09-16 14:22:05 +02:00
2024-11-22 09:21:36 +01:00
2024-11-28 14:34:01 +01:00
2024-11-29 09:19:26 +01:00
2024-11-29 09:19:26 +01:00
2024-11-20 16:30:48 +01:00
2024-10-20 21:47:00 +02:00
2024-08-29 11:02:50 +02:00
2024-12-02 10:05:42 +01:00
2024-01-04 20:37:26 +01:00
2024-07-18 09:34:32 +02:00
2023-10-29 16:43:39 +01:00
2024-11-18 15:00:57 +01:00
2024-11-28 11:44:31 +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
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%