Klaas van Schelven f41f8262c1 EMAIL_USE_SSL: not EMAIL_USE_TLS by default
avoids crashing on "both true" when only `EMAIL_USE_TLS` is explicitly configured

> In your setup those are both true because the former is true by default,
> and the latter is what you have specified. Set the first to false and you
> should be good.

See #86
2025-04-24 21:18:53 +02:00
2025-04-17 22:03:23 +02:00
2025-01-29 13:37:31 +01:00
2025-04-14 11:49:41 +02:00
2024-12-18 09:20:50 +01:00
2025-04-06 15:00:54 +02:00
2025-04-17 22:03:23 +02:00
2025-04-17 22:03:23 +02:00
2025-04-11 11:24:50 +02:00
2025-04-04 17:32:01 +02:00
2025-01-30 15:23:23 +01:00
2025-02-26 16:34:47 +01:00

Bugsink: Self-hosted Error Tracking

Bugsink offers 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.6%
HTML 17.5%
CSS 0.9%
JavaScript 0.6%
Shell 0.3%
Other 0.1%