Klaas van Schelven 2e32ec78a3 Artifact Bundle upload: clean up after extract
for each bundle upload both the chunks and the zipped bundle
were kept (even though they are only needed on-upload, i.e.
after extracting we deal with the extracted files exclusively

This is an important step in 'keeping sourcemaps-related data-usage limited'
i.e. see #129
2025-07-16 20:26:28 +02:00
2025-05-12 10:43:53 +02:00
2025-01-29 13:37:31 +01:00
2025-07-16 10:38:06 +02:00
2025-07-07 12:09:21 +02:00
2025-04-11 11:24:50 +02:00
2025-07-10 11:14:40 +02:00
2025-07-01 13:51:58 +02:00
2025-01-30 15:23:23 +01:00
2025-02-26 16:34:47 +01:00

Bugsink: Self-hosted Error Tracking

Screenshot

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=PUT_AN_ACTUAL_RANDOM_SECRET_HERE_OF_AT_LEAST_50_CHARS \
  -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%