Klaas van Schelven 9a6d453443 Fix 2 bare_base/barest_base mistakes re dark mode
* in 1abc30a760 the hardcoding of ="dark" (during development)
  was accidentally checked in; it never should have been.

* in e14b3eaaa6 I mixed up the bare*base templates. It's actually
  bare_base.html that's for 404/500 etc; barest_base is more bare
  visually (it's the box-based layout for login etc), but it doesn't
  need to be so careful not to use variables.

See #40
2025-07-08 17:04:38 +02:00
2025-05-12 10:43:53 +02:00
2025-01-29 13:37:31 +01:00
2025-05-29 11:11:45 +02:00
2025-07-07 12:09:21 +02:00
2025-07-07 12:09:21 +02:00
2025-04-11 11:24:50 +02:00
2025-06-27 13:01:46 +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%