Klaas van Schelven fad34de68f Move MoreLoudlyFailingTransport out of the default 'eat_your_own_dogfood' conf
it's an extra convinience function for Bugsink developers (me), but the
less stability/more ergonomics tradeoff is not right in the general
case of running Bugsink

(for an example of an actually materializing stability problem, see the
upcoming commit)
2025-02-17 15:27:55 +01:00
2025-01-30 15:04:56 +01:00
2025-02-17 13:41:21 +01:00
2025-01-29 13:37:31 +01:00
2025-02-14 12:25:10 +01:00
2025-02-07 10:21:20 +01:00
2024-12-18 09:20:50 +01:00
2025-01-23 12:14:46 +01:00
2025-02-12 17:11:24 +01:00
2025-02-11 20:24:13 +01:00
2024-12-02 10:05:42 +01:00
2025-01-30 15:23:23 +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%