mirror of
https://github.com/bugsink/bugsink.git
synced 2025-12-30 18:00:17 -06:00
e55c0eb417
See #252 where the following error was triggered: > django.db.transaction.TransactionManagementError: select_for_update cannot be > used outside of a transaction. I believe that this is caused by using a non-sqlite database for the snappea DB. "You probably shouldn't" but at least our own behavior should be consistent. I haven't been able to reproduce this particular error BTW, but at least I've reproduced _some_ error conditions that this commit fixes.
Bugsink: Self-hosted Error Tracking
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.