Klaas van Schelven 5913af4824 Checkbox: restore dark mode to pre-migration behavior
Before the Tailwind 4 migration, checkboxes behaved as follows:

  Light mode
    checked   → cyan bg + white checkmark
    unchecked → white bg
  Dark mode
    checked   → cyan bg + white checkmark
    unchecked → dark bg

In the last commit, we fixed white-on-white, but because we removed
dark:bg-... as well, unchecked boxes in dark mode regressed to white,
standing out like a sore thumb against the dark background.

The current commit adds back the pre-migration behavior; it's not
actually a value-judgement on it other than "it was at least functioning".
(this non-value-judgement is directed at "do I really like cyan bg + white
checkmark in dark mode... I might not)

Fix #225
2025-09-22 20:34:25 +02:00
2025-09-09 16:10:44 +02:00
2025-09-04 13:20:22 +02:00
2025-09-08 14:50:23 +02:00
2025-09-11 09:55:15 +02:00
2025-09-05 22:47:22 +02:00
2025-09-05 22:47:22 +02:00
2025-08-30 15:10:50 +02:00
2025-04-11 11:24:50 +02:00
2025-09-16 12:13:58 +02:00
2025-09-16 10:55:29 +02:00
2025-08-30 15:10:50 +02:00
2025-09-04 11:48:12 +02:00
2025-07-29 12:53:10 +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%