Klaas van Schelven a717dd7374 Truncate input-data that exceeds max_length
Avoiding any (1406, "Data too long for column ...") on MySQL.

For the 'plainly provided' fields I followed the documented maximums which are
also our DB maximums. For calculated_* I harmonized with what Sentry &
GlitchTip both do (and which was already partially reflected in the code), i.e.
128 and 1024.
2025-02-08 21:21:55 +01:00
2025-01-30 15:04:56 +01:00
2025-02-07 17:09:36 +01:00
2025-02-07 16:52:42 +01:00
2025-01-29 13:37:31 +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
2024-08-29 11:02:50 +02: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
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%